It's strongly recommended that Solaris deployments of the Shibboleth SP be built from source, although there are binaries available for Solaris 2.8. Solaris does not come with GCC 3, but various versions can be obtained from Use of GCC is recommended, but new releases of Sun's Forte compiler have been used successfully with some tinkering with configuration scripts. If building your own, GCC must be configured to use Sun's linker. Note that you should use a consistent version of GCC across any other C++ libraries in use within Apache, but other C++ code on your server can freely use a different version as long as the necessary for a given version is available.

1. Prepare the Environment:

A long list of additional software required that changes more frequently is maintained alongside the build instructions.

openssl-0.9.7g , the latest security fix release, has been tested, but any 0.9.7 version should work.

2. Install Shibboleth:

Shibboleth should usually be built from source on Solaris. To build the actual module, please follow the separate build directions before continuing on.

There is a set of binaries available for Solaris 2.8 available from the main download site that you may attempt to use. It's strongly discouraged to use these in production.

3. Configure Shibboleth:

Add the newly compiled or installed modules to Apache next.

  1. Edit httpd.conf :
  2. /opt/shibboleth/sbin/shibd must be independently started and run in order to handle access requests. In most cases, the build process ensures that shibd can locate the configuration file and schemas, but the SHIBCONFIG and SHIBSCHEMAS environment variables may be used as well. Command line options can also be used to specify them.
  3. By default, the Shibboleth module is configured to log information on behalf of Apache to /var/log/httpd/native.log , though this can be changed by modifying the .logger files pointed to by the configuration. For this log to be created, Apache must have permission to write to this file, which may require that the file be manually created and permissions assigned to whatever user Apache is configured to run under. If the file does not appear when Apache runs with the modules loaded, check for permission problems or change the location used.
  4. shibd creates its own separate logs at /var/log/shibboleth/shibd.log and must have appropriate write permissions itself as well.

At this point, you should have a fully functional SP, but before it can be tested, you'll need to configure it to interoperate with an !IdP. Many federations will provide these for their community, and TestShib is available for anyone to test with.