SSO changes after refresh on lower environment
search cancel

SSO changes after refresh on lower environment


Article ID: 220380


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


You have SSO in all your environments. How do you proceed with a refresh and disaster recovery (DR)?

If you ensure that these tables (CMN_SEC_CERTS and CMN_SEC_SAML_CONFIGS) are backed up and restored in the lower environment, can you avoid disrupting the SSO connectivity in the lower environment?


Release : Any


What you have to do after restore

  • Ensure SSO is checked in CSA
  • Ensure SAML feature is enabled with the command
  • For lower environments, we recommend keeping the existing tables CMN_SEC_CERTS and CMN_SEC_SAML_CONFIGS because Prod tables will interrupt connectivity.
  • After the restore, the DBA must delete the entries in CMN_SEC_CERTS and CMN_SEC_SAML_CONFIGS and copy the entries from the backed-up tables