We're having trouble with a Java application running alongside SSO. The method Thread.currentThread().getContextClassLoader() returns null when SSO is running but works when SSO is not running. Many other places in the code that use runtime class loading fail as well. I assume our app is running in a totally separate JVM. Is SSO manipulating our VM somehow? Is there an SSO setting that would alleviate this problem?
Thanks for any hints.
SSO is enforced on the perimeter with Identity being asserted in the WLS container i.e. OAM Identity Assertion Provider creates a JaaS Subject for the user identity in the OAM_REMOTE_USER header. I suspect the "null' value is the result of something missing or misconfigured in your deployment.
Sorry, I didn't understand a word of that. I'm not a user of SSO but a client of ours is using it and conflicting with our software somehow. I can't explain why our software works when SSO isn't running but doesn't work when SSO is running. Not sure how that indicates something being misconfigured in our deployment. I'm trying to determine what SSO is doing (if anything) to cause class loading errors in our totally separate JVM. The only difference between our app working and not working seems to be whether SSO is running or not.