We have recently configured SSO in our DEV environment and we have also DB refreshed our DEV environment with Prod DB. What we have noticed is that the URL on which we have configured SSO is down but the non SSO url is up and working fine.
Can you think of any possibility because of which SSO url will stop working after the DB refresh?
Clarity 16.x ON-PREMISE
Product functioning as per design. Following a DB refresh activity the SAML configuration has to be redone on the DEV environment.
Here is an excerpt from the product documentation- Configuring SAML 2.0:
Clarity uses the CMN_SEC_CERTS and CMN_SEC_SAML_CONFIGS tables to store SAML details in the database. If you have setup SAML 2.0 authentication on a development or test system and copy the production data to these systems, you need to: