Configuration of External Authentication Systems page
Repository > 
> External Authentication
Purpose of the page¶
This page makes it possible to set up communication with external authorisation systems such as the LDAP system, and determine how user data is imported from the various systems.
Page fields
The fields displayed for communication with the external LDAP system are shown below.
| Field | Description |
|---|---|
| Use Third Party Authentication | Enables the use and configuration of communication with the various external systems and displays the necessary fields. |
| Available authentication types | Makes it possible to select the external system with which to configure communication. |
| General Settings | |
| Fail Safe authentication enabled | The user can access CCH Tagetik using their own credentials even if the external system is not responding. |
| Enabled Login for all users of external authentication mechanism | All users authenticated on the external system will be added to the Repository and can therefore access CCH Tagetik. |
| Password rule for open an external user | Password rule that a user from an external system must follow if they become a local user. |
| Customized URL for redirect after Logout | URL to which users are redirected after disconnecting from CCH Tagetik. |
| Specific Settings | |
| Update User data on Login | Every time a user connects, the relative data in the Repository will be updated with the data on the LDAP system. |
| Read profiles from LDAP | The user’s roles and rights will be inherited directly from the LDAP system. |
| Filter: User name | Script for recovering the user name based on the user name entered at login. |
| Domain rule | Script for recovering the domain name based on the domain name entered at login. |
| Browse LDAP with specific user | Makes it possible to set the user who by default runs the user search on LDAP. |
| Configuration sets | |
| Opens the window of requirements to be configured for the LDAP servers. = configuration complete = configuration incomplete, required data are missing. For more details on configuring these requirements, see the documentation on integration with the LDAP system. |