Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Currently we do not offer custom installation and configuration documentation for the Shibboleth IDP v4 software – the upstream documentation covers everything and in more detail than we ever could.

...

Existing IDP v4 installation

In case you're already still running a Shibboleth IDPv3 IDP v4 in eduID.at you must upgrade to IDPv4 IDP v5 before end of August 2024 CE by installing the v4 v5 software over your v3 v4 software.

Note

The upgrade instructions of the Shibboleth IDPv4 IDP software make it very clear that this is the only supported way to get from IDPv3 IDP v4 to v4v5.

That also entails first upgrading your IDPv3 IDP to the latest/last IDPv3 IDPv4 release available and cleaning up /modernising your configuration until no more "DEPRECATED" messages are shown in your IDP's log files.

Make sure to review the relevant documentation before doing so changing anything, particularly:

You're free to rebuild your IDP server from scratch (as always using the current Debian "stable" version, as always) but instead of also installing a "cleanfresh" version of IDPv4 you must first IDP v5 copy over your IDPv3 IDP v4 installation (/opt/shibboleth-idp) to the new server and only then install IDPv4 IDP v5 to the same location. (Of course you may copy more stuff over, such as your Tomcat configuration and existing TLS keystore to be used by Tomcat as webserver, etc.)

Completely new IDP installation

In case you have not been running a Shibboleth IDP in eduID.at so far you can install a "fresh" instance of IDPv4. We do not provide specific (copy/paste-able) instructions on how to do that at this time.IDP v5.

The instructions we provide should get you up and running somewhat quickly with proper support for the most relevant community standards and practicesOne way to make up for this would be for you to install the latest/last IDPv3 release according to our instructions and then upgrade that to v4 following the upstream documentation and the above hints.