...
For other RPM-supporting Linux versions, you can usually rebuild the SRPM packages.
Warning | |
---|---|
title | Use the Correct RPM or not at allUnder no circumstances should you attempt to install a set of RPM packages built for/with a different OS or version from your own (apart from the CentOS/RHEL exception noted above). This will usually lead to unpredictable problems and support issues. Instead, you can rebuild the SRPM packages. |
Warning |
---|
Incompatibility with RHEL / CentOS 7.0-7.3RHEL Red Hat and CentOS 7.4 include included a newer version of OpenSSL than 7.0-7.3, and due to an inadvertent rebuild of one package by the SUSE Build Service, the packages for that OS had to be fully rebuilt, which means they no longer the official packages don't support versions older than 7.4. A full yum update to the new OS will include the update to these packages, but updating to them or installing them from scratch will fail if the OS version is older than 7.4. We apologize for the inconvenience but the problem was impossible to recover from. |
Installing via Yum
The supported approach is to add a yum repository referencing the Shibboleth Project mirror sites alongside your existing OS-supplied repository. This allows you to manage the Shibboleth packages in a standard way and pick up updates using a single command.
...
Installation varies by OS, but usually you just drop the definition file into a directory such as /etc/yum.repos.d
. You can turn the repository on and off by adjusting the "enabled" property in the file, such as to prevent automated updates and maintain manual control. While enabled, the yum command will "see" the Shibboleth packages when you perform standard operations, and installing the SP should require only a single command:
32 bit OS
Code Block | ||||
---|---|---|---|---|
| ||||
$ yum install shibboleth |
64 bit OS
Code Block | ||||
---|---|---|---|---|
| ||||
$ yum install shibboleth.x86_64 |
Warning |
---|
Be careful of accidentally installing both the 64-bit and 32-bit version on a 64-bit server. The yum repository contains both versions for some OSs and the OS will think it can install both. |
After Installation
The RPM installation process will place various components of Shibboleth in appropriate default directories based on your operating system's file system layout. Typically:
Shibboleth configuration files will be placed at /etc/shibboleth/ and the necessary Apache configuration in /etc/httpd/conf.d/shib.conf
shibd will be installed to /usr/sbin and may be managed using service and chkconfig (on System V platforms) or with systemctl (on systemd platforms, some additional information available).
An version of mod_shib.so appropriate to the OS-supplied Apache and other pluggable modules will be installed to /usr/lib/shibboleth/ on a 32-bit OS and /usr/lib64/shibboleth on a 64-bit OS.
Basic Configuration
In httpd.conf:
Use of the
<RequestMap>
feature is not needed for use with Apache, but if you must, its use absolutely requires that theUseCanonicalName
Apache directive be set.Ensure that the
ServerName
directive in each virtual host is properly set, including overriding the scheme or port as required by any load balancing, proxying, or offloading you may be doing.
Restart Apache.
/usr/sbin/shibd must be independently started and run in order to handle requests. The daemon should be loaded and monitored along with all other major services.
By default, the Shibboleth module is configured to log information to the local syslog, with a subset also to the Apache error log.
The shibd service creates its own separate logs in /var/log/shibboleth. This is the most important log used for debugging anything regarding the SP and most problems manifest here rather than on the web server side.
...