Maintain SAML/SSO 2.0 during pushing prod to test

[Thilo Brause]

We changed our productive system to use SAML  / SSO 2.0 to authenticate users as primary authentication method. Part of the authentication configuration is the URL of our Jira-Instance.

If we restore a Jira-Backup from our productive system to our testing system, then the configuration of SSO (containing the productive systems URL) would not match to the testing systems URL. Resulting in any authentication attempt to fail, preventing us to log in on the testing system.

Is there any way to maintain/retain the SSO configuration of a testing system when restoring into it a backup of the productive system?

[Thilo Brause · Accepted solution]

After a lot of analysis we found that the biggest part of the configuration of out testsystem is in the Jira database, including the configuration of SSO. So pushing prod to test is done by copying the database and then applying a SQL-Script which resets all values different in the testsystem to the correct values. Setting the correct certificate for sso for example results in the following query:

{code}

update propertytext set propertyvalue='-----BEGIN CERTIFICATE----- ABCDEFG -----END CERTIFICATE-----' where ID in (select ID from propertyentry where PROPERTY_KEY='com.atlassian.plugins.authentication.sso.config.signing-cert');

{code}