This document describes how to configure, compile, and install the Shibboleth components
on Solaris 10. The SP is built to run under the native apache2 server. Components that
use SSL are linked with the native OpenSSL libraries. All executables and libraries are
built with a runtime library path so that LD_LIBRARY_PATH is not necessary. This is the
recommended practice for Solaris. Additional components all install into /usr/local.

SP Components

I have versions of these scripts that I used under Opensolaris 2009.6 with Shib 2.1. See geneva.rutgers.edu/shib21-opensolaris.tar. They assume (1) ssl is in /usr/local/ssl, (2) apache 2.2 installed from the repository, (3) shib goes into /usr/local/shibboleth. --hedrick@rutgers.edu

Installation

Some components will need to be installed so that others can be built. This is noted
in the configure scripts. All components can be installed with either `make install'
or by executing the make script with the `install' option. At my university, we don't
install them directly but build packages first, and then install them from the packages.
If there is interest, I can make these packages available. They are compiled for the
x86 flavour of Solaris 10 only.

Apache2 configuration

On Solaris 10, all apache2 configuration files reside in /etc/apache2. You will have
to insert:

Include /usr/local/etc/shibboleth/apache2.config

into ssl.conf. Just before:

#   Pass Phrase Dialog:

is a good place. As well, you will have to comment out this line in the same file:

SSLCryptoDevice pkcs11

This prevents a mysterious interaction with the Shibboleth module that causes CGI
execution to hang because apache is waiting on a mutex.

`shibd' should be started at boot time. On Solaris 10, this is done with an SMF
manifest. These typically reside in /var/svc/manifest. The `site' subdirectory is
a suitable place for locally-added manifests.

Log files for the apache module are defined in /usr/local/etc/shibboleth/native.logger.
Likewise, for shibd they are defined in /usr/local/etc/shibboleth/shibd.logger. These
can be changed to more suitable locations, or the /usr/local/var/log/shibboleth directory
can be replaced to a symlink, to /var/log/shibboleth for example.