...
By design, the idp.home/edit-webapp directory can be used to preserve changes across upgrades, but if you modify an existing file (as opposed to adding files), you should always compare your changed versions to the upgraded files to understand if any changes are important, though we will make every effort to highlight any such changes in the ReleaseNotes.
Be aware that rolling upgrades are generally guaranteed to work only for patch upgrades (changes in the final digit). Minor upgrades may sometimes include internal changes to storage formats or other implementation details that could prevent certain features from working interoperably between versions. It is best to either plan for a relatively fast rolling upgrade within a maintenance window, or plan for a short period of downtime.
Windows Upgrade
The installer available for Microsoft Windows handles upgrades from older releases. See the Windows Upgrade topic for instructions. This also supports upgrading Jetty, if that option was selected.
...
- Download the latest Identity Provider software package (the zip file has Windows line endings, the tarball Unix line endings).
- Unpack the archive you downloaded to a convenient location. It will not be needed after installation.
- Change into the newly created distribution directory, shibboleth-identityprovider-VERSION
- Run either ./bin/install.sh (on non-Windows systems) or .\bin\install.bat (on Windows systems).
- Make sure to specify the same installation directory you used originally (the idp.home directory). This will cause the installer to perform an upgrade. Using a different installation directory will essentially perform a new installation.
- After reviewing any necessary changes, rebuild the warfile with any edits you've applied by running either idp.home/bin/build.sh or idp.home\bin\build.bat.
- Re-deploy the new IdP warfile, located in idp.home/war/idp.war.
...