Upgrading Global SSO v2.0 - 2.2.0
When you upgrade your SSO plugins to 2.2.0 version, ensure that you perform the following operations:
- Ensure that you upgrade all plugins at once. That is if you have Global SSO for Jira, Confluence, and Bamboo, you need to upgrade all three tools at the same time.
- We changed the encryption type, therefore, during the SAML Consumer configuration step, set the Secret Key field for the encryption.
- Make sure that you first migrate your test environments to Global SSO 2.2.0. This is necessary for rare cases when the database isn't migrated for some reason. See Troubleshooting section for instructions.
- Check whether the certificate text was migrated correctly. To do this, you can take a look at your certificate on the IDP side or in the metadata.xml file which is exported from the IDP.
Troubleshooting data migrations
To check whether your data was migrated correctly, try accessing SAML Consumer configuration page. If you can't access it, perform the following steps:
- Go to Administration > Manage Add-Ons, uninstall Global SSO plugin and SSO Consumer plugin (installs automatically with each SSO plugin).
- Go to the database and back up data from the SAMLconfig table, it should contain "SAMLconfig" in the name of the table.
- Delete this table from the database.
- Install Global SSO 2.2.X.
- Go to Administration > Add-Ons >SAML Consumer Configuration page and configure SAML Consumer.
Upgrading Global SSO v2.2.0 and higher
Starting with Global SSO v2.2.0, you can upgrade the SSO plugins just using the regular UPM functionality (Upgrade button).