Thursday, January 7, 2010

Troubleshooting OAM-OAAM integration

1. Error:
Oracle Access Manager Operation Error
The login form /oasa/loginPage.jsp defined for form authentication itself requires form authentication. It should be unprotected.
Contact your website administrator to remedy this problem.
Probable Solution:
Disable the policy protecting the /oasa/loginPage.jsp (if exists). Restart both webserver and access server.
2. Error:

UnsatisfiedLinkError: no obaccess in java.library.path (in webserver logs)
Probable Solution:
Add this E:\product\oracle\NetPoint\AccessSDK\AccessServerSDK\oblix\lib to the tomcat (where OASA is hosted) path variable. If the server hosting OASA application is weblogic, add this to startWeblogic.cmd to the LD_LIBRARY_PATH variable.

No comments:

Post a Comment