My Oracle Support Banner

Intermittent SAML Attribute Profile not Working Correctly with ArtifactResolve in OAM Federated Cluster - Attributes are Sometimes not Populated Correctly (Doc ID 2420090.1)

Last updated on JULY 23, 2018

Applies to:

Oracle Access Manager - Version 11.1.2.3.0 and later
Information in this document applies to any platform.

Symptoms

Intermittent SAML Attribute Profile not Working Correctly with ArtifactResolve in OAM Federated Cluster - Attributes are Sometimes not Populated Correctly

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 stickyness 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.

Changes

 

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!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.