Table 12. Cannot log in to the Tivoli Enterprise Portal Server (continued)
Problem Corrective action and solution
If the Tivoli Enterprise Portal Server
connection to LDAP is lost.
When the portal server is configured to authenticate against the LDAP
server (with optionally enabled Single Sign-On capability), if you lose the
portal server to LDAP connection, this will cause any log in attempt to fail
with error code KFWITM393E: "User ID or password is invalid". This
authentication failure will be reported for any user, including the default
administrative user "sysadmin", and not only for users defined in the LDAP
repository.
Re-establish the connection to LDAP. As soon as the portal server to LDAP
connection is re-established, you can log in to the Tivoli Enterprise Portal.
If there is still a problem connecting with LDAP, de-configure LDAP
authentication.
If the LDAP connection is broken and the normal procedure to switch off
LDAP-based authentication does not work, the following steps need to be
performed:
1. For AIX and Linux systems, stop the portal server with the ./itmcmd
agent stop cq command invoked from the installation directory.
2. Run the ./disableLDAPRepository.sh script from candle_home/arch/iw/
scripts, where arch is the system architecture, for example "li6263" or
"aix533."
3. Reconfigure the portal server and disable LDAP authentication using the
./itmcmd config -A cq command invoked from the installation
directory.
4. Start the portal server with the ./itmcmd agent start cq command
invoked from installation directory. The portal server authentication
through the monitoring server is now enabled.
5. If the monitoring server was also configured to use LDAP and the
reason for this procedure being applied is LDAP being out of service,
ensure you also change the monitoring server configuration to not
authenticate through LDAP, following steps from the monitoring server
configuration help.
1. For Windows systems, stop the portal server service using the Manage
Tivoli Enterprise Monitoring Services application. \
2. Run the disableLDAPRepository.bat script from candle_home\CNPSJ\
scripts.
3. Reconfigure the portal server using the Manage Tivoli Enterprise
Monitoring Services application and disable the "Validate User with
LDAP" option.
4. Start the portal server service using the Manage Tivoli Enterprise
Monitoring Services application. The portal server authentication
through the monitoring server is now enabled.
5. If the monitoring server was also configured to use LDAP and the
reason for this procedure being applied is LDAP being out of service,
ensure you also change the monitoring server configuration to not
authenticate through LDAP, following the steps from the monitoring
server configuration help.
Cannot connect to the portal server
Review the problems and resolutions when you have trouble with the connection
to the Tivoli Enterprise Portal Server.
Chapter 6. Connectivity troubleshooting 117
To Next Page
Loading...
Need help?
General
