Settings
(1) Login, Username: The login is the name with which you log on to the client. The user name is internal (usually the real/full name of the user).
(2) LDAP ID: The LDAP identifier (directory service user for the initial connection to the LDAP server). For Windows Active Directory a typical entry is Domain\Username. OpenLDAP or other LDAP systems typically expect entries like cn=username,cn=users,ou=groups,dc=test,dc=com.
The following listing shows the entry in file ./etc/startup.xml that has to exist so that a user can log on to Lobster Integration via LDAP. Here, the LDAP-Alias (here win2k3) and the fallback user (normal Lobster Integration user, here admin) are specified. If there is an configureLDAP entry in this file, the normal password stored for the Lobster Integration user will not be used when logging on to the Lobster Integration client. Instead, the authentication is done via LDAP. If the LDAP server is not available, the fallback user (and its password set in the user administration of Lobster _data) will be used for the login to Lobster Integration. Note: Optionally, a REST admin fallback user can be specified. This user would then only be given the user right Administration via REST.
<!-- LDAP (alias and fallback user name in case of broken LDAP server connection --><Call name="configureLDAP"> <Arg type="String">win2k3</Arg> <Arg type="String">admin</Arg></Call><!-- Optional REST admin fallback in case LDAP connection is broken --><!-- <Set name="fallbackRESTAdminUserName"></Set> -->(3) Password: These buttons allow you to enter a password and to view it in plaintext. Note: It is possible to define a password policy (i.e. how a password must be formed) for Lobster Integration users in configuration file ./etc/startup.xml. The following section has to be added to element <New class="com.ebd.hub.datawizard.app.DataWizard">. The first argument is the regular expression that defines how the password has to be formed. The second argument is the error message in case the entered password is not correct. Note: The string & in this section is the escape sequence for the character & in XML files.
<!-- sample password policy; define regex and error message --><Call name="setPasswordPolicy"> <Arg>^(?=.*[0-9])(?=.*[a-z])(?=.*[A-Z])(?=.*[@#$%!&-+=()])(?=\S+$).{5,20}$</Arg> <Arg>Password must be 5 to 20 chars and contains at least one digit, upper, lower and special char!</Arg></Call>(4) Mail: The default address for profile error emails and for emails from the add-on Workflow.
(5) Clients: The clients for which the user is authorised. A user with admin rights is always authorized for all clients.