Difference between revisions of "Seon Core web interface"

From Seon
Jump to: navigation, search
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

Revision as of 08:29, 5 September 2012

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 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. /var/www/seon) create a textfile named ".htaccess" 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. /var/www/seon) named ".htaccess":

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"

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. "username1", "username2" and "username3"), the line starting with "require " must contain a white-space separated list of these allowed usernames:

require user username1 username2 username3