Removing deprecated authentication mechanisms

If your Pure installation is setup to use one of the deprecated authentication mechanisms, the installation of 5.30.0 and above will fail and you need to install the previous version again.

NOTE: The installation fails before any migration is done, so no need to roll back the database etc., just install the same version as before the attempt to install Pure 5.30.0.

NOTE2: The team who is primarily assisting on issues with authentication are on a reduced capacity from 15th to 29th of July, so we highly advice customers to not install 5.30.0 in production in one of those two weeks.

To avoid this, switch to SAML2, an Elsevier Authentication type OR disable any deprecated authentication mechanism before the upgrade.

As part of the 5.29.0 version, you will receive a warning if an unsupported authentication mechanism is enabled, furthermore you can access and check your current setup. The following screenshot shows how to access it and which mechanisms will not cause the upgrade to fail:

I.e. all five authentication mechanisms listed on the screenshot will not cause the upgrade to fail.

Maintaining your staging auth setup when copying database

If your staging Pure installation is setup differently than your production, it is now possible to persist this setup even when copying a production database dump to staging.

This is done by following the following steps:

1. Request Elsevier support user to do the following (as it is not available to “normal” administrators):
   1. Login to the target Pure, navigate to Administrator → Configuration
   2. Download the configuration called “Saml2ProviderConfiguration”, be careful, as there are similar named ones.
2. On the servere where Pure is installed, you need to use this file on the command line with the “-DConfiguration.xml” parameter, e.g. -Dconfiguration.xml=/purefiles/saml_conf.xml