...
However, it is possible for newer releases to introduce changes that deprecate older configuration options or formats, and you are encouraged to review this page for any changes required to "modernize" your configuration after an upgrade to make production support simpler, and future upgrades smoother. Some new features may also depend on making these changes.
| Table of Contents |
|---|
Shibboleth 2.4.1 Configuration Changes
The following represent new default settings and other significant configuration changes made since the 2.4.0 release.
SVN Support Now Requires Separate Download
IMPACT: high
After review, the project has determined that we are unable to distribute TMate's SVNKit software library, and have therefore been forced to remove it from the Shibboleth IdP distribution. As a result, deployers relying on the SVNResource type for access to configuration files (in service.xml) or for metadata in (relying-party.xml) cannot upgrade to this release without taking the additional step of downloading and adding the svnkit jar to thelib directory in the unpacked distribution before running the installation/upgrade script. The library can be obtained directly from http://svnkit.com/. Note that the latest versions are compatible only with newer subversion working copy formats and existing deployments may need to use the older 1.3 release that had been shipped with the software in the past.
Shibboleth 2.4.0 Configuration Changes
The following represent new default settings and other significant configuration changes made since the 2.3.8 release.
...