Common Security Access Manager problems

Check the following information for issues with any of the following Security Access Manager base components:

Environment information messages in the server log file at startup
In Security Access Manager, the severity level of the startup environment dump information added to the server process log is WARNING.
Unable to create new user
Unable to authenticate user
After you create a user, this user cannot authenticate immediately with the new Security Access Manager user identity until the account is modified.
Unexpected access to resources
Accesses to a protected system resource are either being unexpectedly granted or denied. It is always wise to first validate that the Security Access Manager processes are started and running normally.
Password change does not work in a multidomain environment
Specific configuration conditions for policy server, subdomains, and WebSEAL can cause password changes to fail.
Product pages might not display in browser if website is not trusted
Product pages might not display in a browser if the website is not trusted. For example, if the administrative console pages for Security Access Manager are empty even though the product is working, the issue might be caused by an untrusted website.
Errors occur with in pdjrte startup when Java 2 security is enabled
Errors might occur at application startup when Java 2 security is enabled.
Network connectivity issues or unresponsive interfaces
Configuring multiple interfaces on the same subnet might cause certain interfaces to appear unresponsive or other network connectivity issues.

Parent topic: Troubleshooting