I am engulfed in Oracle Identity & Access Management domain. I have expertise in providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., for on-prem and cloud deployments.
I am here to share troubleshooting tips, discuss architecture and design aspects, integration scenarios and many more that I have experienced with.
Earlier I had written my comments about OES 11g with java SM in Tomcat container in this post. I'd like to redefine this with some changes.
First of all, OES 188.8.131.52.0 is not supported on Tomcat Server 6.x. However if your client have no choice other than using Tomcat and there is an application to be protected against OES 11g, then here is what you can do:
Assuming that OES server and client + Java SM is installed and up and running.
Goto Tomcat install directory, edit the setclasspath.sh or setclasspath.bat and update the Tomcat Classpath with oes-client.jar as export CLASSPATH=$CLASSPATH:$OES_CLIENT_HOME/modules/oracle.oes.sm_11.1.1/oes-client.jar.
Specify the Java SM jps-config.xml in the Java OPTIONS (in the same file setclasspath.sh or setclasspath.bat) as export JAVA_OPTS= $JAVA_OPTS -Doracle.security.jps.config=$OES_CLIENT_HOME/oes_sm_instances//config/jps-config.xml.
Test the Tomcat application with some authorization policies and it works!
Exceptions: In my case, our enterprise application was using xml parser jars which was conflicting with xmlparserv2.jar located under $OES_CLIENT_HOME/modules/...