Site specific configuration on Windows - CustomerID

NOTE: This step is very important as some configuration options cannot be changed after this step.

Creating a site specific configuration for Ubisecure CustomerID can be done by editing the custom/eidm2.properties and other Ubisecure CustomerID configuration files. For more information about the configuration options, refer to Configuration - CustomerID. If you will be using Active Directory as the main user repository for Ubisecure CustomerID then you can find AD specific configuration guidance from AD integration configuration - CustomerID.

Examples of the types of configurations required include:

defining user registration workflows
defining organization types and roles
defining what strong authentication methods are available
defining policies for login names

Generally it is recommended to use a very basic eidm2.properties configuration first, ensure the system is fully configured and running and then modify the settings again later to match the use case requirements.

Execute the following commands to create and edit the eidm2.properties file:

Editing eidm2.properties

cd /d %PROGRAMFILES%\Ubisecure\customerid\application\custom
notepad eidm2.properties

Typical entries include:

Creating basic eidm2.properties

# use email address as the username when logging in
# this requires that directory.account.login=mail is added to password.2 authentication method settings
# without this setting, the default uid is used as the username when logging in
general.login.attribute = mail

# where to redirect the user when an error occurs or user presses exit - generally home page of the target service
general.default.returnUrl = https://www.example.com

# where to redirect the user after logout has been performed
general.default.logoutReturnUrl = https://www.example.com