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:
The action URL specified for this authentication scheme should be unprotected using Anonymous authentication scheme. For instance, if you had specified the action param as shown here (action: /dummy) in the form authentication scheme, then you should create a new policy domain and add /dummy resource, specify anonymous authentication scheme in the Default Rules, Specify allow all in the authorization Rule. However, you will need to upgrade OAM to 10.1.4.2 if you are using the older version.
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.
About the Author Mahendra
I am engulfed in Oracle Identity & Access Management domain. I have expertise on providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., I am also well versed with complex integrations within Identity Management and other product domains. I have expertise on building demos and implementation experience on products Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlement Server, Oracle Virtual Directory, Oracle Internet Directory etc., Look @ my blog: http://talkidentity.blogspot.com