DIGIPASS Authentication for Epic Hyperspace Administrator Guide Configuring DIGIPASS Authentication Module
4.3
Configuring the Authentication Server
4.3.1
Client Record
A client record must be configured in the authentication server for the DIGIPASS Authentication Module. The configuration wizard can create the required record if a connection to the authentication server and an administrator account with sufficient privileges are available. If the configuration wizard does not create a client record, this must be done manually.
•
Component type should be set to
Epic Hyperspace .
•
Location should be set to the same IP address as in the Connect from IP address setting in the
DIGIPASS Authentication for Epic Hyperspace Configuration Center.
•
Select a policy for the authentication server to use when processing authentication requests from the
DIGIPASS Authentication Module.
4.3.2
Configuring for Windows User Accounts
4.3.2.1
Windows user name resolution
If the authentication server is installed on a Windows platform and is using an ODBC database (including the embedded database) as its data store, it is recommended that you enable Windows user name resolution. This allows the authentication server to use Windows functionality to resolve a user ID – as entered during a login in the format username@domain or domain\username – into a user ID and domain. It is highly recommended if
Dynamic User Registration (DUR)
will be enabled.
This setting is not required where the authentication server is using Active Directory as its data store – name resolution will occur automatically.
This setting is not available on IDENTIKEY Authentication Server on Linux or IDENTIKEY Appliance / IDENTIKEY
Virtual Appliance.
If the
Use Windows user name resolution
feature is disabled or unavailable, it is essential that users always use the same login name. If they try to log in using a different form of their Windows account name, their login will be rejected, unless a second DIGIPASS user account has been created in the master domain.
4.3.2.2
Case sensitivity
Windows user names are not case-sensitive. If the ODBC database used by the authentication server is casesensitive, ensure that the user ID case is converted to lower case. Upper case may also be used, but will involve extra configuration steps. The embedded PostgreSQL database is set to convert to lower case by default. For more information, refer to the IDENTIKEY Authentication Server Administrator Guide, Section
“Encoding and Case Sensitivity”.
42
