My Oracle Support Banner

OAM : Federation :global Logout Fails In PROD Env As OAM Is Not Sending In Relaystate With Response. (Doc ID 2498752.1)

Last updated on MARCH 25, 2019

Applies to:

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

Symptoms


OAM 11.1.2.3.180116 Federation global logout fails on the Service Provider end with error HTTP 404 when more than 2 oam servers in cluster that is acting as IDP.

The issue can be reproduced at will with the following steps:
1. Configure Federation with OAM as IDP and SAP as SP
2. Have more than 3 OAM Servers in a cluster
3. Perform SP initiate logout sequence

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!


In this Document
Symptoms
Changes
Cause
Solution
References


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