Page Comparison

...

1. In httpd.conf:
   
   • Shibboleth includes sample snippets in /opt/local/etc/shibboleth for each version of Apache. Do not include these files directly but copy the relevant portions to your own Apache configuration files/strategy.
   • Use of the <RequestMap> feature is not needed for use with Apache, but if you must, its use absolutely requires that the UseCanonicalName 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.

2. Restart Apache.

3. The port install process generates and installs a launchd descriptor to use in starting and monitoring shibd. You can manually start and stop it yourself, or you can use launchctl like so:

   Code Block
   launchctl load -F /Library/LaunchDaemons/org.macports.shibd.plist launchctl unload -F /Library/LaunchDaemons/org.macports.shibd.plist

   If you want shibd to start upon boot, run:

   Code Block
   launchctl load -Fw /Library/LaunchDaemons/org.macports.shibd.plist

   
   

4. By default, the Shibboleth module is configured to log information to the local syslog, with a subset also to the Apache error log.

5. The shibd service creates its own separate logs in /opt/local/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.

...