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 184.108.40.206.180116 and later
Information in this document applies to any platform.
OAM 220.127.116.11.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
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