IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Enable user authentication
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
LDAP user authentication through the portal server
You can configure the Tivoli Enterprise Portal Server to use an LDAP user registry to authenticate users.
This is required if you intend to provide single sign-on (SSO) capability for these scenarios:
- The Tivoli Enterprise Portal is launched from other web-based applications and you don't want users to re-enter their credentials.
- The Tivoli Enterprise Portal is used to launch other web-based or web-enabled applications and you don't want users to re-enter their credentials.
- IBM Dashboard Application Services Hub is used to display monitoring data retrieved using the dashboard data provider component of the portal server. Best practice is to use single sign-on in this case, so that dashboard users can launch the Tivoli Enterprise Portal and user don't have to re-enter their credentials. Additionally, single sign-on must be used if you want to control authorization to monitored resources on a per user basis.
- The IBM Tivoli Monitoring charting web service is being used by another application such as Tivoli Integrated Portal.
- Prerequisites for configuring LDAP authentication on the portal server
- About single sign-on
- Roadmap for setting up the portal server to use an LDAP user registry and single sign-on
- Use Manage Tivoli Enterprise Monitoring Services to configure the portal server for LDAP authentication
- Use the Linux or UNIX command line to configure the portal server for LDAP authentication
- Use the TEPS/e administration console
- Map Tivoli Enterprise Portal user IDs to LDAP distinguished names
- Reconfigure the browser client for SSO
- Import and export LTPA keys
- Manage new LDAP users
- Disable LDAP authentication on the portal server
Parent topic:
Enable user authentication