The configuration file config/authentication.conf
in the NameSurfer directory tree contains
a number of configurable settings in a simple, human-readable text
format. It is read by the the NameSurfer HTTP server process on startup.
Changes made to this file will not take effect until the process is killed and restarted.
Each setting is entered on a line of its own as a "name: value" pair.
Empty lines and comments beginning with a # character are allowed.
If the use_external_auth option in
webui.conf is not enabled, this configuration file will
not be read on startup at all.
The allowed options in this configuration file depend on the supported authentication methods,
which are LDAP, Radius and Tacacs in the current standard NmeSurfer package. Each of the methods
has its own set of configuration options which need to be present in this file if that
method is used.
The external authentication method to be used for authenticating users. Corresponding
method-specific configuration options will be read from this configuration file.
The following settings are supported for the LDAP authentication:
When configuring for simple AD authentication, all LDAP configuration options except this and the ldap_uri should be left blank to ensure correct operation.
If set, the given user will be used to do the initial binding to the LDAP server before conducting the search for the actual user name used for NameSurfer access. If not defined, the binding will be attempted using the account name given to NameSurfer login.
If the base location for user accounts is different from the initial LDAP binding base
(when a separate binding user is used), this field must contain the correct search path. If
this value is not set, the base DN value will be used for the actual user data search.
If defined, a value that must be present in the user's access field value to allow
login to NameSurfer. If access field is not defined,this parameter has no effect
either.
The following settings are supported for the Radius authentication: