This topic explains how to create a task for integrating with an LDAP, establishing a routine for importing the database of users, groups, and assets from a certain domain. This integration is also useful because it allows users from a separate domain to authenticate in the system.
The system can be integrated with Active Directory, Apache DS, and Novell eDirectory, which use the LDAP protocol. Also, the system will occasionally scan for new objects to import. Once an object is imported, the system will not replicate any future modifications made to it on the LDAP server. The duration of this integration task may vary according to some external variables, namely: the data traffic on the network, the directory’s infrastructure (number of forests and domains), number of objects (users, groups, and assets), among others. For structures in which the integration task takes a long period of time, it’s best to schedule the task when traffic on the network is low.
To integrate the system so that authentication is handled via an external directory (Active Directory), see Appendix -> Integrating Authentication through an LDAP -> How to Integrate Authentication via Active Directory. To integrate the system to authenticate though Novell eDirectory, see Appendix -> Integrating Authentication through an LDAP -> How to Integrate Authentication via Novell eDirectory. To use a federation service that uses the WS-Federation or SAML 2.0 protocols, get in touch with the support team.