Skip Navigation
Expand
SSO on upgrade sites
Answer ID 12893   |   Last Review Date 09/06/2024

I set up SSO on my upgrade site, do I need to change anything back before cutover?

Environment:
 
Oracle B2C Service SSO
 
Resolution:
 
Depending on what type of SSO you have set up on your upgrade site, you will need to revert some of the changes you have made to your SSO set up on the upgrade site prior to cutover.  Specifically changes to certificates uploaded into the file manager and changes to configuration settings.  The file manager and configuration settings, excluding the SSO_ENTITY_ID configuration setting, carry forward from the upgrade site during cutover and if you do not revert changes to these to areas, SSO may not work as expected on the production site post cutover.  
 
If you have configured SSO on your upgrade site, please see details below on which site features are carried forward from during cutover; 
 
Production site:
  • The SSO_ENTITY_ID configuration setting is a unique setting in that the value from this configuration setting is carried forward from the production site during cutover. When the upgrade site is created, the value in this configuration setting on the upgrade site will be blank.  Two sites cannot have the same value in the SSO_ENTITY_ID configuration setting otherwise SSO will not work as expected.  You can update the SSO_ENTITY_ID configuration setting on your upgrade site if you are testing SSO.  See Change SSO entity ID for more information.  
  • The Identity Provider set up in the Single Sign-On Configurations component will carry forward from the production site during cutover.
Upgrade site:
  • The SSO certificates uploaded in the File Manager will carry forward from the upgrade site during cutover.  
  • The value in the SAML_20_SIGN_CERTS configuration setting will carry forward from the upgrade site during cutover.  
  • The value in the PTA_EXTERNAL_LOGIN_URL configuration setting will carry forward from the upgrade site during cutover.