About Using IPv6 Troubleshooting Tips for OAM Provider Deployments

Configuring Single Sign-On Using Oracle Access Manager 10g 16-75

16.8.13 Login Form is Shown Repeatedly Upon Credential Submission: No Error

This issue typically points to an incorrect user name or password. No error is shown. Ensure that you are supplying the correct user name and password. The user login name must be the value of the attribute that is configured in the Form Login authentication scheme. For example, Challenge Parameter creds: userid.

16.8.14 Logout and Session Time Out Issues

When a user logs out, or a user session times out, the user should be challenged for reauthentication. However, the following might occur instead: ■ Logout: After logging out, if the user attempts to access the application in the same browser window the application is still accessible without reauthenticating. ■ Session Time Out: After a user session time out, the user is challenged to reauthenticate. However, if the user gives a different user ID he is granted the same privileges as the previous user. The ObSSOCookie is still present. Some configuration must be done at the application level to kill the ObSSOCookie. For proper behavior, WebLogic application session time out values should be the same as WebGate session time out values. If setting up an Identity Asserter in the WebLogic Application Console, the Web application using the Identity Asserter must have its auth-method set to CLIENT-CERT. For more information, see Configuring OAM Identity Assertion for SSO with Oracle Access Manager 10g on page 16-34.

16.8.15 Not Found: The requested URL or Resource Was Not Found

If you receive a message stating that the requested URL or resource was not found on this server, the reverse proxy Web server might not be forwarding requests to the Oracle WebLogic Server. To ensure that the reverse proxy is forwarding requests to Oracle WebLogic Server

1. Locate the httpd.conf file on the reverse proxy WebGate Web server. For example:

ORACLE_INSTANCEconfigOHSohs_namehttpd.conf 2. Confirm the correct settings to forward requests to the correct host and port of the Oracle WebLogic Server: httpd.conf IfModule mod_weblogic.c WebLogicHost host WebLogicPort yourWlsPortNumber IfModule Location request-uri-pattern SetHandler weblogic-handler Location

16.8.16 Oracle WebLogic Server Fails to Start

If the Oracle WebLogic Server fails to start, you can take the following actions.