1. Configure the system to use Apache 2.2.x, according to other pages on this wiki.
  2. Check that the install of OpenSSL has the development extensions. If the system received a custom build of OpenSSL, there will be a /usr/local/ssl directory, and this step can be skipped.
    1. Check the rpmlogs for openssl-devel. Install it if it is missing.
      grep openssl-devel /var/log/rpmpkgs
      yum install openssl-devel
      
  3. Download the source code tarball and build script from either Trogdor or the /mit/webauth/shibboleth/source webauth Athena locker.
    1. Download from Aether:
      cd /home/www/tmp
      scp $troguser@trogdor.mit.edu:/opt/software-repository-tmp/Touchstone/shibboleth-sp-1.3.1-sources.tgz .
      
    2. Download for the webauth Athena locker:
      cd /home/www/tmp
      scp athena.dialup.mit.edu:/mit/webauth/shibboleth/source/shibboleth-sp-1.3.1-sources.tgz .
      
  4. Make certain that the correct version of apxs from httpd-devel packages are installed.
  5. Create a Shibboleth build directory, unpack the tarball into it, and run the build script.
  6. Configure Shibboleth, as described in Configuring+and+customizing+the+Shibboleth+SP.
  7. Add the init script to /etc/init.d, and set to run on appropriate runlevels.
    cd /home/www/shibboleth/etc/shibboleth
    cp /home/www/shibboleth/etc/shibboleth/shibd-redhat /etc/init.d/shibd
    chmod u+x,a-w /etc/init.d/shibd
    cd /etc/init.d
    ln -s /etc/init.d/shibd /etc/rc.d/rc3.d/S45shibd
    ln -s /etc/init.d/shibd /etc/rc.d/rc4.d/S45shibd
    ln -s /etc/init.d/shibd /etc/rc.d/rc5.d/S45shibd
    ln -s /etc/init.d/shibd /etc/rc.d/rc3.d/K45shibd
    ln -s /etc/init.d/shibd /etc/rc.d/rc4.d/K45shibd
    ln -s /etc/init.d/shibd /etc/rc.d/rc5.d/K45shibd
    /etc/init.d/shibd start
    
  8. At a convenient time, bounce Apache and related web services.
    /etc/init.d/web stop
    /etc/init.d/web start
    
  9. Send email to the Touchstone support team (touchstone-support@mit.edu), asking for the system to be included in the Touchstone database. Information they need is hostname, CN name if different from hostname, technical support contact (using a list is preferred, for our group, map-support@mit.edu is normally used), the organization that owns the system, and a short description (one sentence) of what function this server will perform.