Seon Core web interface - Revision history

Admin: /* Securing with LDAP / ActiveDirectory */

2012-09-05T08:37:46Z

‎Securing with LDAP / ActiveDirectory

Admin: /* Securing with given username and password */

2012-09-05T08:35:29Z

‎Securing with given username and password

Admin at 08:35, 5 September 2012

2012-09-05T08:35:18Z

Admin at 08:29, 5 September 2012

2012-09-05T08:29:03Z

Admin at 15:54, 1 May 2012

2012-05-01T15:54:06Z

Admin at 15:53, 1 May 2012

2012-05-01T15:53:26Z

Admin at 15:53, 1 May 2012

2012-05-01T15:53:01Z

Admin: Replacing page with '== Configuration == The Seon web interface uses the global Seon configuration file "`/etc/seon.conf`". This file is expected in exactly this location. If this is not...'

2012-05-01T15:52:47Z

Replacing page with '== Configuration == The Seon web interface uses the global Seon configuration file "<code>/etc/seon.conf</code>". This file is expected in exactly this location. If this is not...'

Admin: /* enabling user view */

2009-10-17T14:52:53Z

‎enabling user view

Admin at 20:10, 11 May 2007

2007-05-11T20:10:19Z

@@ Line 29: / Line 29: @@
 === Securing with LDAP / ActiveDirectory ===
 If you have an LDAP based directory service available (i.e. openLDAP, Microsoft Active Directory, IBM Lotus Notes etc.) you can authenticate users via your centralized user storage.
 Example configuration file in web interface directory (i.e. <code>/var/www/seon</code>) named "<code>.htaccess</code>":

@@ Line 26: / Line 26: @@
   Re-type new password:
   Adding password for user username2
 === Securing with LDAP / ActiveDirectory ===

@@ Line 7: / Line 7: @@
 === Securing with given username and password ===
 In the web interface directory (i.e. <code>/var/www/seon</code>) create a textfile named "<code>.htaccess</code>" with this content:
 === Securing with LDAP / ActiveDirectory ===

← Older revision		Revision as of 08:29, 5 September 2012
Line 1:		Line 1:
	== Configuration ==		== Configuration ==
	The Seon web interface uses the [[Seon Core main configuration file\|global Seon configuration file "<code>/etc/seon.conf</code>"]]. This file is expected in exactly this location. If this is not the case in your environment, please contact Seon support at contact@seon.de.		The Seon web interface uses the [[Seon Core main configuration file\|global Seon configuration file "<code>/etc/seon.conf</code>"]]. This file is expected in exactly this location. If this is not the case in your environment, please contact Seon support at contact@seon.de.
		+
		+	== Securing with password ==
		+	The easiest way to secure the Seon administrative web interface in an Apache environment is to use the authentification method via ".htaccess". There areseveral options available, the two most common ways are shown here.
		+
		+	=== Securing with given username and password ===
		+	In the web interface directory (i.e. <code>/var/www/seon</code>) create a textfile named "<code>.htaccess</code>" with this content:
		+
		+
		+	=== Securing with LDAP / ActiveDirectory ===
		+	If you have an LDAP based directory service available (i.e. openLDAP, Microsoft Active Directory, IBM Lotus Notes etc.) you can authenticate users via your centralized user storage.
		+
		+	Example configuration file in web interface directory (i.e. <code>/var/www/seon</code>) named "<code>.htaccess</code>":
		+	<pre>
		+	AuthType Basic
		+	AuthName Internal
		+	AuthBasicAuthoritative off
		+	AuthBasicProvider ldap
		+	AuthzLDAPAuthoritative off
		+	AuthLDAPURL ldap://192.168.0.1/OU=ou-seon-admin,DC=de,DC=company,DC=net?sAMAccountName??(objectclass=*)
		+	require valid-user
		+	AuthLDAPBindDN "CN=seon,OU=admins,OU=ou-admins,DC=de,DC=company,DC=net"
		+	AuthLDAPBindPassword "pwd"
		+	</pre>
		+	Explanation of the configuration variables:
		+	*AuthLDAPURL: defines the connectivity of the LDAP server via IP address or hostname, also contains the information where to search for valid users
		+	*AuthLDAPBindDN: configuration of the connecting user who has the permission to search for the given user
		+	*AuthLDAPBindPassword: password of the connecting user defined at "AuthLDAPBindDN"
		+
		+	If you want to allow only a list of special usernames (i.e. "<code>username1</code>", "<code>username2</code>" and "<code>username3</code>"), the line starting with "<code>require </code>" must contain a white-space separated list of these allowed usernames:
		+	require user username1 username2 username3

← Older revision		Revision as of 15:54, 1 May 2012
Line 1:		Line 1:
	== Configuration ==		== Configuration ==
−	The Seon web interface uses the global Seon configuration file "<code>/etc/seon.conf</code>". This file is expected in exactly this location. If this is not the case in your environment, please contact Seon support at contact@seon.de.	+	The Seon web interface uses the [[Seon Core main configuration file\|global Seon configuration file "<code>/etc/seon.conf</code>"]]. This file is expected in exactly this location. If this is not the case in your environment, please contact Seon support at contact@seon.de.

← Older revision		Revision as of 15:53, 1 May 2012
Line 1:		Line 1:
	== Configuration ==		== Configuration ==
−	The Seon web interface uses the global Seon configuration file "<code>/etc/seon.conf</code>". This file is expected in exactly this location. If this is not the case in your environment, please contact Seon support at [contact@seon.de].	+	The Seon web interface uses the global Seon configuration file "<code>/etc/seon.conf</code>". This file is expected in exactly this location. If this is not the case in your environment, please contact Seon support at contact@seon.de.

← Older revision		Revision as of 15:52, 1 May 2012
Line 1:		Line 1:
	== Configuration ==		== Configuration ==
−	The Seon ~~Core administrative~~ web interface ~~is configured via~~ the ~~file~~	+	The Seon web interface uses the global Seon configuration file "<code>/etc/seon.conf</code>". This file is expected in exactly this location. If this is not the case in your environment, please contact Seon support at contact@seon.de.
−	~~database.inc.php~~
−	~~where the first lines are intersting only:~~
−	~~<pre>~~
−	~~<?php~~
−	~~// Since 21.10.2006, you have two options to configure your web interface:~~
−	~~// - by pointing to an~~ Seon configuration file ~~(like~~ "/etc/seon.conf")
−	/~~/ - by typing in the database connection values directly~~
−	~~// The type of used configuration is defined in the variable "config_type" using either "file" or "direct~~".
−	~~// Using the "~~file~~" method only works if the web interface~~ is ~~located at the same host as Seon is running!~~
−
−	~~$config_type="file";~~
−	~~// $config_type="direct";~~
−
−	~~$config_file="/etc/seon~~.~~conf";~~
−
−	~~// confguration part for direct configuration: just uncomment the following 5 lines and change values as needed~~
−	~~// $mysql_host = "localhost:3306:/tmp/mysql.sock";~~
−	~~// $mysql_user = "seon";~~
−	~~// $mysql_password = "seon";~~
−	~~// $DBName = "seon";~~
−	~~// $tableprefix="seon_";~~
−	~~// $serverID = 0;~~
−
−	~~// enable this flag if a user-sight of~~ this ~~web interface~~ is ~~wanted~~
−	~~// valid values: true/false~~
−	~~// $userview=true;~~
−	~~// $userview=false;~~
−	~~</pre>~~
−
−	~~== enabling user view ==~~
−	~~"User view" is a special mode of~~ the ~~web interface where all administrative operations are disabled and only interesting views of the Seon web interface are enabled.~~
−
−	~~By setting the variable "<code>$userview</code>" to "<code>true</code>"~~, ~~the following components change:~~
−	*the header of the web interface disables interacting with the daemons (starting, stopping, dumping logs etc.)
−	*Configuration is viewable, but not changeable
−	*CAPI configuration is viewable, but not changeable. Scanning new devices is disabled.
−	*OFTP2 cipher suites and their configurations (including variable definitions) are disabled completely.
−	*Tools (database backup, license update & overview, automatic certificate generation) are disabled completely.
−	*Partner overview only contains basic OFTP parameters and no functionality to create, edit and/or delete entries. Seon ~~Enterprise functionality is disabled. Links to statistics for partners are enabled.~~
−	*Send log doesn't contain links to edit partner parameters any more.
−	*Receive log doesn't contain links to edit partner parameters any more.
−	*xERP log doesn't contain links to edit partner parameters any more.
−	*Script logs doesn't support ~~restarting events any more.~~
−	*Send queue doesn't contain any editing functionality. ~~Creating new entries is disabled~~. ~~Deleting is enabled. Mass-actions are disabled. Aborting active transfers is enabled. Viewing the progress is enabled.~~
−	*Receive queue has no delete- and abort-functionality. Link to edit partner parameters removed.
−	*All additional Seon Enterprise specific links have been removed.
−	*all unlinked PHP scripts contain a check for accessibility. In user view mode, the abort with the message "''You are not allowed to view this page!''".
−	*Automatic certificate import behaviour is unavailable

← Older revision		Revision as of 14:52, 17 October 2009
Line 48:		Line 48:
	*All additional Seon Enterprise specific links have been removed.		*All additional Seon Enterprise specific links have been removed.
	*all unlinked PHP scripts contain a check for accessibility. In user view mode, the abort with the message "''You are not allowed to view this page!''".		*all unlinked PHP scripts contain a check for accessibility. In user view mode, the abort with the message "''You are not allowed to view this page!''".
		+	*Automatic certificate import behaviour is unavailable

@@ Line 44: / Line 44: @@
 *xERP log doesn't contain links to edit partner parameters any more.
 *Script logs doesn't support restarting events any more.
-*Send queue doesn't contain any editing functionality. Creating new entries is disabled. Deleting is disabled. Mass-actions are disabled. Aborting active transfers is enabled. Viewing the progress is enabled.
+*Send queue doesn't contain any editing functionality. Creating new entries is disabled. Deleting is enabled. Mass-actions are disabled. Aborting active transfers is enabled. Viewing the progress is enabled.
 *Receive queue has no delete- and abort-functionality. Link to edit partner parameters removed.
 *All additional Seon Enterprise specific links have been removed.
 *all unlinked PHP scripts contain a check for accessibility. In user view mode, the abort with the message "''You are not allowed to view this page!''".

Seon Core web interface - Revision history

Admin: /* Securing with LDAP / ActiveDirectory */

Admin: /* Securing with given username and password */

Admin at 08:35, 5 September 2012

Admin at 08:29, 5 September 2012

Admin at 15:54, 1 May 2012

Admin at 15:53, 1 May 2012

Admin at 15:53, 1 May 2012

Admin: Replacing page with '== Configuration == The Seon web interface uses the global Seon configuration file "/etc/seon.conf". This file is expected in exactly this location. If this is not...'

Admin: /* enabling user view */

Admin at 20:10, 11 May 2007

Admin: Replacing page with '== Configuration == The Seon web interface uses the global Seon configuration file "`/etc/seon.conf`". This file is expected in exactly this location. If this is not...'