Sun Access Manager 6.3 -403 ERRORS WHILE USING AGENT 2.X ON IBM WEBSPHERE
(Doc ID 1290561.1)
Last updated on MAY 13, 2012
Applies to:Oracle OpenSSO - Version 6.3 and later
Information in this document applies to any platform.
J2EE Agent on Web Sphere and other Application Servers
While accessing protected applications which are protected by J2EE Agents on IBM WebSphere or any other Application Servers and if URL_Policies are in place for accessing the protected applications, 403 forbidden errors may be noticed by the user.
Some sections of the Agent debug logs may have the following signature traces (amWebPolicy)
<PolicyRequest appSSOToken="AQIC5wM2LY4SfcyRkUUOyrRHcHu9mqc2Zt3Uhfw1GU3TGys=@AAJTSQACMDE=#" requestId="0">
<GetResourceResults userSSOToken="AQIC5wM2LY4Sfcxfb3u1a8jrdlITS8JKNMxMd2HR1CaBvhA=@AAJTSQACMDE=#" serviceName="iPlanetAMWebAgentService"
If you encounter such errors along with 403 forebidden errors check the amclientsdk.jar and agent.jar files contained in the Application library path are same from the Agent binaries which are being deployed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document