Using single sign-on
The EngageOne Deliver application can be configured to integrate with an LDAP server for authentication. The LDAP server will be connected to your existing corporate database (or some shared repository). User profiles are imported from the shared resource and used by EngageOne Deliver to auto-populate its user database. The main advantage of integrating with a LDAP server is that you don’t have to re-enter your existing personal details currently stored on your corporate database. Your profile, including your password and roles, will automatically be copied to the EngageOne Deliver database. The personal details copied are the following:
- User Name - This is mandatory to be present in the corporate database.
- First Name
- Initials
- Last Name
- Job Title
- Email – This is mandatory to be present in the corporate database
- Phone
- Fax
If the mandatory fields are not present in the corporate database, an error message will be displayed and you cannot log in to EngageOne Deliver.
Each time you log in, LDAP’s auto-population function is triggered and its data will be reflected on the EngageOne Deliver database. Theoretically, this will allow easy switching from LDAP authentication back to the built-in EngageOne Deliver authentication and vice versa.
Update of personal details is not bi-directional. This means that updates on personal details made outside EngageOne Deliver will always be reflected in EngageOne Deliver when you log in; however, changes made inside EngageOne Deliver will not change the LDAP repository. Any change made on your personal details inside EngageOne Deliver will remain in the EngageOne Deliver database until the next time you log in.
Auditing of changes in user information is currently not supported by EngageOne Deliver.
Functions in EngageOne Deliver that change when LDAP is enabled:
- Passwords generated for new users will be ignored by EngageOne Deliver.
- The Update password function is not available.
- The Forgotten password function is not available.