Post Quarterly Update Single Sign On (Federated SSO) is No Longer Working (Doc ID 2979036.1)

Last updated on OCTOBER 05, 2023

Applies to:

Symptoms

You have configured custom Identity Provider Policies and Sign-On Policies for each environment - TEST, DEV and PROD.

This is done by creating new Identity Provider Policies and/or Sign-On Policies and by assigning the corresponding Application on the last step of configuring the policies. There is an Application corresponding to each environment. The name of the application is “OTMGTM_” followed by the environment name that was specified when creating the environment. 

Post the quarterly these Sign-On policies are no longer working.

Changes

With 23C, OTM started doing Quarterly Updates using our near-zero downtime architecture. At a very high level the upgrade downtime is significantly reduced by installing the new OTM version on a new instance ahead of the downtime cutover. The new instance requires a new IDCS Enterprise App to be created. If a customer is configuring their Federated SSO differently for each environment (Production, Test, Dev), then they will have assigned each existing Enterprise App to a different Sign-On Policy than the recommended Default Sign-On Policy.

Cause

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