Intermittent SAML Attribute Profile not Working Correctly With ArtifactResolve in Oracle Access Manager 11g R2PS3 (OAM 11.1.2.3) Federated Cluster - Attributes Are Sometimes not Populated Correctly
(Doc ID 2420090.1)
Last updated on NOVEMBER 15, 2023
Applies to:
Oracle Access Manager - Version 11.1.2.3.0 and laterInformation in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.
Symptoms
Intermittent SAML Attribute Profile not Working Correctly with ArtifactResolve inOracle Access Manager 11g R2PS3 (OAM 11.1.2.3) Federated Cluster - Attributes are Sometimes not Populated Correctly
- Using OAM as SAML IDP and the SAML SP clients are required to work with SAML v2 artifact binding.
- Works fine as long as only 1 oam server active, but as soon as the 2nd oam server is active in the cluster that the artifact resolve is sometimes failing to retrieve session information of the logged in user.
- Flow
The problem occurs only when the SAML AuthN request (via a browser) is hitting one oam server, and the SAML ArtifactResolve request (via SOAP service from SP) is hitting the other oam server.
In this situation the SAML Response is still returned to the SP, however the asserted attributes defined in the SP Attribute Profile are not populated and left empty.
ERROR case - In the ERROR case the SAML AuthN hitting <OAM_SERVER2> and the SAML ArtifactResolve hitting <OAM_SERVER1>. The SAML SP performs a SOAP/XML request towards OAM according the the SAML 2.0 specification. The request in the logs, including the OAM response to the request. Its just that the attributes are not populated.
- Note that it is not possible to create some kind of stickiness over both SAML requests, since one is done via a browser, and the other is done via the SAML SP via SOAP.
- SAML with SOAP (Artifact Binding) does work with OAM in a High Available cluster. The artifact resolve (SOAP) is working in general, it is just that the attributes are sometimes not populated correctly via the attribute profile.
Cause
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
Symptoms |
Cause |
Solution |