Date: Thu, 28 Mar 2024 23:43:28 +0000 (UTC) Message-ID: <1126588909.1.1711669408266@0c9fabf88774> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_351401574.1711669408251" ------=_Part_0_351401574.1711669408251 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Shibboleth can be built on most versions of 32- and 64-bit Linux= , but is officially supported only on the following distributions at this t= ime, using the RPM packages available from the project's official mirrors:<= /p>
Red Hat Enterprise 7/8/9
CentOS 7
Rocky Linux 8/9
Amazon Linux 2
Amazon Linux 2023
Packages for CentOS 8 are still being produced but the platform is no lo= nger supported officially due to it having transitioned to an unstable floa= ting package set, and the packages may stop working at any time.
See the SystemRequirements page for more de= tail on this.
The official packages are built for, and integrate with, only the Apache= (httpd) package that is supplied with the OS. When building from source or= SRPM, you can accomodate any version of Apache (or its derivations) that i= s compatible.
Information about SELinux
If your distribution supports the RPM package manager, it is strongly su= ggested that you install using RPMs built for your specific distribution, o= r by rebuilding the SRPM source packages provided. If this is not possible,= you can build from source.
Under no circumstances should you attempt to install a set of RPM packag= es built for/with a different OS or version from your own (aside from the R= HEL/CentOS/Rocky cases). This will usually lead to unpredictable problems a= nd support issues. Instead, just rebuild the SRPM packages and make sure yo= u have a repeatable process to incorporate security patch updates promptly.=
Recent Linux versions occasionally provide an in-place upgrade path. Whe= ther this works or not, it will not upgrade your Shibboleth packages nor wi= ll it properly adjust the yum/dnf repository file, resulting in failure. If= you wish to do this, uninstall the SP first and then reinstall it with the= proper repository file afterward.
Upgrading to new SP releases is handled automatically when RPMs are used= , or in the case of a source build when "make install" is run using the sam= e installation prefix. The system prevents configuration files from being o= verwritten and skips "initial install" tasks like generating keys. In the c= ase of RPM upgrades, services should be appropriately restarted, but with s= ource builds that step has to be done manually.