Oracle Access Maanger (OAM) Federation - OAM Console Shows The Wrong "Validity" Date
(Doc ID 2945385.1)
Last updated on SEPTEMBER 26, 2024
Applies to:
Oracle Access Manager - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
The OAM console shows the wrong "Validity Date" for the IdP
- Oracle Access Manger (OAM) is the Service Provider (SP)
- Azure is the Identity Provider (IdP)
- Imported metadata supplied by the IdP, which contained a new certificate
- The federated flow works as expected (No loss of functionality)
The issue is that the OAM console for this IdP shows the old "validity date" and not the new one, why?
Changes
Imported new IdP metadata with new signing certificate
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 |