IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Enable user authentication > LDAP user authentication using Microsoft Active Directory
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Roadmap overview
To integrate the IBM Tivoli Monitoring user authentication environment with your site's Active Directory implementation, complete the steps outlined in this topic.
- Plan and create monitoring server and portal server users within Active Directory
Follow the steps outlined in this topic.
- Create and configure the portal server user accounts and permissions, if desired
Skip this step: If you do not want to use an LDAP server to authenticate Tivoli Enterprise Portal users and you do not need to configure single sign-on for integration with other products such as IBM Dashboard Application Services Hub.
Use either the Tivoli Enterprise Portal Administer Users interface or the tacmd command-line interface, if your site requires portal server user authentication.
These user accounts will use LDAP for authentication; thus, the userids chosen must exactly match those specified in Active Directory. For the attributes you should choose, see Figure 3.
- Enable and configure LDAP user authentication for the portal server, if desired
Skip this step: If you do not want to use an LDAP server to authenticate Tivoli Enterprise Portal users and you do not need to configure single sign-on for integration with other products such as IBM Dashboard Application Services Hub.
Complete this step if your site requires portal server authentication.
- Configure TEPS/e for TLS/SSL, if necessary
Typically, TEPS/e is TLS/SSL enabled by default. If configure TLS/SSL communication between the portal server and the LDAP server use the TEPS/e administration console.
- Enable and configure LDAP user authentication for the monitoring server, if desired
Skip this step: If you do not want to use an LDAP user to authenticate your monitoring server users.
Complete this step if your site requires monitoring server authentication.