Last updated on SEPTEMBER 21, 2016
Applies to:Oracle OpenSSO - Version: 7.1
Information in this document applies to any platform.
J2EE Policy Agent
This problem can happen when either OpenSSO is deployed in an alternate path ( other than the default context root /opensso ) or Sun Java System Access Manager 7.1 is used (here is the context root /amserver ).
The access manager's amNaming debug log reports the following:
URLChecker.check(): setting status to AVAILABLE for http[s]://[hostname]:[port]/opensso/namingservice
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms