Reverting Kantega SSO Enterprise from a breaking change version

Owned by Elias Brattli Sørensen
Last updated: Dec 04, 2024
3 min read

Generally, we recommend taking a backup (snapshot of config) before making an update of the add-on. If you did, you can follow the instructions in https://kantega-sso.atlassian.net/wiki/x/NACGQQ , and then restore the backup of config taken in the given version.

Platform 7: newer versions need a system parameter set

If you need to downgrade on a newer product running platform 7, like Confluence 9, Jira 10, Bitbucket 9 or Bamboo 10, then file upload on UPM has been disabled by default. To re-enable file upload, set stop the product, set the following JVM startup parameter and restart: -Dupm.plugin.upload.enabled=true

Example: downgrade from major version 5.0.2 back to 4.14.6

Revert Kantega SSO from a version that introduced breaking changes, after you migrated the configuration with Update of config.

The first 3 steps of this guide are not relevant if you did not get an update of config warning. When performing a non-breaking downgrade, simply skip to step 4.

  1. When clicked “update configuration”, a snapshot of config was taken automatically, now under

Snapshots of config (Backup & restore)

2. Select the snapshot / backup taken before upgrade of config, and click restore. Now the failed update of config is reset to what you had before, and your instance should be revertible to the version you came from.

3. Download the previous stable version of Kantega SSO Enterprise from Atlassian Marketplace, in our example 4.14.6. You find this under versions and clicking See all ... versions on the app listing:

 

4. Uninstall Kantega SSO Enterprise under Manage Apps:

5. Upload the previous stable version, in our example 4.14.6.

 

6. Go to Kantega SSO Enterprise and check now whether SSO is working by performing a login test. The system should now be back in its previous state.