Deployment of Shibboleth Service Provider (SP) 2.4.3 on
Solaris from sources

X.509 certificate

A valid certificate is required for decrypting SAML assertions and/or establishing SSL connections to Identity Providers.
Please refer to http://www.switch.ch/aai/certificates/ for further information about certificates and certificate requirements.
The same certificate can be used by the web server and by the Shibboleth Service Provider. However, it is recommended that Shibboleth uses a self-signed certificate whereas the web server should use a certificate from a well-known CA.
Please follow the steps described below to create a self-signed certificate for between the Shibboleth components. See SWITCHaai Certificate Acceptance Policy.

libcurl SSL/TLS support

The Shibboleth Service Provider requires that the libcurl library is linked against openssl and not gnutls.

Apache HTTP 2.2

For configuration, see at the Apache HTTP documentation in the references.

NTP

Servers running Shibboleth must have their system time synchronized in order to avoid clock-skew errors:

Shibboleth build environment

Since the Shibboleth Service Provider is implemented in C/C++, some C/C++ build tools are needed
(e.g. Sun Studio C/C++ Compiler from the packages SPROcc and SPROcpl.

if [ -L /opt/shibboleth-sp2 ] ; then sudo rm /opt/shibboleth-sp2 ; fi;
sudo ln -sf $SHIB_HOME /opt/shibboleth-sp2

# Load the shibboleth module

LoadModule mod_shib /opt/shibboleth-sp/lib/shibboleth/mod_shib_22.so

# Global Configuration
# This is the XML file that contains all the global, non-apache-specific
# configuration.  Look at this file for most of your configuration parameters.
ShibConfig /etc/shibboleth/shibboleth2.xml

# Used for example logo and style sheet in error templates.
<IfModule mod_alias.c>
  <Location /shibboleth-sp>
    Allow from all
  </Location>
  Alias /shibboleth-sp/main.css /opt/shibboleth-sp/share/doc/shibboleth-2.4.3/main.css
  Alias /shibboleth-sp/logo.jpg /opt/shibboleth-sp/share/doc/shibboleth-2.4.3/logo.jpg
</IfModule>

...
...
# This file is generated from envvars-std.in
#

export LD_LIBRARY_PATH=/opt/shibboleth-sp/lib

sudo a2enmod shib

cp $SHIB_HOME/etc/shibboleth/shibd-debian /etc/init.d/shibd 

PATH=/sbin:/bin:/usr/sbin:/usr/bin
DESC="Shibboleth 2 daemon"
NAME=shibd
SHIB_HOME=/opt/shibboleth-sp/
SHIBSP_CONFIG=/etc/shibboleth/shibboleth2.xml
LD_LIBRARY_PATH=$SHIB_HOME/lib
DAEMON=$SHIB_HOME/sbin/shibd
SCRIPTNAME=/etc/init.d/$NAME
PIDFILE=/var/run/$NAME.pid

...

chmod +x /etc/init.d/shibd
cd /etc/init.d
ln -s shibd /etc/rcS.d/K28shibd
ln -s shibd /etc/rc0.d/K28shibd
ln -s shibd /etc/rc1.d/K28shibd
ln -s shibd /etc/rc2.d/K28shibd
ln -s shibd /etc/rc3.d/S15shibd

mkdir /etc/shibboleth/ 

cp $SHIB_HOME/etc/shibboleth/native.logger /etc/shibboleth/ 
cp $SHIB_HOME/etc/shibboleth/shibd.logger /etc/shibboleth/ 
cp $SHIB_HOME/etc/shibboleth/syslog.logger /etc/shibboleth/ 

mkdir -p /var/log/shibboleth/ 
touch /var/log/shibboleth/shibd.log 
touch /var/log/shibboleth/native.log 
touch /var/log/shibboleth/native_warn.log 
chgrp www-data /var/log/shibboleth/native.log 
chmod g+w /var/log/shibboleth/native.log 
chgrp www-data /var/log/shibboleth/native_warn.log 
chmod g+w /var/log/shibboleth/native_warn.log 

if [ -L /opt/shibboleth-sp2 ] ; then rm /opt/shibboleth-sp2 ; fi;
ln -sf $SHIB_HOME /opt/shibboleth-sp2

<SPConfig xmlns="urn:mace:shibboleth:2.0:native:sp:config"
    xmlns:conf="urn:mace:shibboleth:2.0:native:sp:config"
    xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
    xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"    
    xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"
    clockSkew="180">

    <!--
    By default, in-memory StorageService, ReplayCache, ArtifactMap, and SessionCache
    are used. See example-shibboleth2.xml for samples of explicitly configuring them.
    -->

    <!-- The OutOfProcess section contains properties affecting the shibd daemon. -->
    <OutOfProcess logger="/etc/shibboleth/shibd.logger"/>

    <!--
    The InProcess section contains settings affecting web server modules.
    Required for IIS, but can be removed when using other web servers.
    -->
    <InProcess logger="/etc/shibboleth/native.logger">
        <ISAPI normalizeRequest="true" safeHeaderNames="true">
            <!--
            Maps IIS Instance ID values to the host scheme/name/port. The name is
            required so that the proper <Host> in the request map above is found without
            having to cover every possible DNS/IP combination the user might enter.
            -->
            <Site id="1" name="sp.example.org"/>
            <!--
            When the port and scheme are omitted, the HTTP request's port and scheme are used.
            If these are wrong because of virtualization, they can be explicitly set here to
            ensure proper redirect generation.
            -->
            <!--
            <Site id="42" name="virtual.example.org" scheme="https" port="443"/>
            -->
        </ISAPI>
    </InProcess>

    <!--
    To customize behavior for specific resources on Apache, and to link vhosts or
    resources to ApplicationOverride settings below, use web server options/commands.
    See https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPConfigurationElements for help.
    
    For more examples of the RequestMap XML syntax instead, see the example-shibboleth2.xml
    file, and the https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPRequestMapHowTo topic.
    -->
    <RequestMapper type="Native">
        <RequestMap applicationId="default">
            <!--
            The example below requires a session for documents in /secure on the containing host with http and
            https on the default ports. Note that the name and port in the <Host> elements MUST match
            Apache's ServerName and Port directives or the IIS Site name in the <ISAPI> element
            below.
            -->
            <Host name="sp.example.org">
                <Path name="secure" authType="shibboleth" requireSession="true"/>
            </Host>
        </RequestMap>
    </RequestMapper>

    <!-- The ApplicationDefaults element is where most of Shibboleth's SAML bits are defined. -->
    <ApplicationDefaults entityID="https://sp.example.org/shibboleth"
                         homeURL="https://sp.example.org/"
                         REMOTE_USER="uniqueID persistent-id targeted-id"
                         signing="back" requireTransportAuth="false">

        <!--
        Controls session lifetimes, address checks, cookie handling, and the protocol handlers.
        You MUST supply an effectively unique handlerURL value for each of your applications.
        The value defaults to /Shibboleth.sso, and should be a relative path, with the SP computing
        a relative value based on the virtual host. Using handlerSSL="true", the default, will force
        the protocol to be https. You should also add a cookieProps setting of "; path=/; secure"
        in that case. Note that while we default checkAddress to "false", this has a negative
        impact on the security of the SP. Stealing cookies/sessions is much easier with this disabled.
        -->
        <Sessions lifetime="28800" timeout="3600" 
            checkAddress="false" consistentAddress="true"
            relayState="ss:mem" handlerSSL="true"
            cookieProps="; path=/; secure; HttpOnly">

            <!--
            In order to use a default Identity Provider add an attribute like:
            entityID="https://idp.example.org/shibboleth"
            to the SSO element. It's value should be the entityID of the
            default Identity Provider. 
            -->
            <SSO discoveryProtocol="SAMLDS" discoveryURL="https://wayf.switch.ch/SWITCHaai/WAYF">
              SAML2 SAML1
            </SSO>

            <!-- SAML and local-only logout. -->
            <Logout>SAML2 Local</Logout>

            <!--
            In addition to the standard SessionInitiator it is also possible
            to define custom SessionInitiators to enforce specific settings.
            More information is available at:
            https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPSessionInitiator
            -->

            <!--
            <SessionInitiator type="Chaining" Location="/DS" id="DS" relayState="cookie" isDefault="true">
                <SessionInitiator type="SAML2" acsByIndex="false" acsIndex="1" template="bindingTemplate.html" />
                <SessionInitiator type="Shib1" acsIndex="5"/>
                <SessionInitiator type="SAMLDS" URL="https://wayf.switch.ch/SWITCHaai/WAYF"/>
            </SessionInitiator>
            -->            
            
            <!-- Extension service that generates "approximate" metadata based on SP configuration. -->
            <Handler type="MetadataGenerator" Location="/Metadata" signing="false"/>

            <!-- Status reporting service. -->
            
            <!-- 
            Please note that the IP 130.59.138.32 is used by the AAI Resource Registry. 
            By allowing the Resource Registry to periodically access the status handler, 
            it is possible to monitor this Service Provider and to specifically alert 
            administrators in case of configuration or security relevant issues.
            If you feel uncomfortable with this, set acl="127.0.0.1"
            -->
            <Handler type="Status" Location="/Status" acl="127.0.0.1 ::1 130.59.138.32"/>

            <!-- Session diagnostic service. -->
            <Handler type="Session" Location="/Session" showAttributeValues="false"/>

            <!-- JSON feed of discovery information. -->
            <!--
            <Handler type="DiscoveryFeed" Location="/DiscoFeed"/>
            -->
        </Sessions>

        <!--
        Allows overriding of error template information/filenames. You can
        also add attributes with values that can be plugged into the templates.
        -->
        <Errors supportContact="aai@example.org"
            logoLocation="https://www.switch.ch/aai/design/images/SWITCHaai.gif"
            styleSheet="https://www.switch.ch/aai/design/shib-error.css"/>
        
        <!-- Example of locally maintained metadata. -->
        <!--
        <MetadataProvider type="XML" file="partner-metadata.xml"/>
        -->
        
        <MetadataProvider type="XML" validate="true"
            uri="http://metadata.aai.switch.ch/metadata.switchaai.xml"
            backingFilePath="/etc/shibboleth/metadata.switchaai.xml"
            reloadInterval="3600">
            <MetadataFilter type="RequireValidUntil" maxValidityInterval="604800"/>
            <MetadataFilter type="Signature" verifyName="false">
                <TrustEngine type="StaticPKIX"
                    certificate="/etc/shibboleth/SWITCHaaiRootCA.crt.pem"
                    verifyDepth="2" checkRevocation="fullChain"/>
            </MetadataFilter>
        </MetadataProvider>

        <!-- Map to extract attributes from SAML assertions. -->
        <AttributeExtractor type="XML" validate="true" reloadChanges="false" path="/etc/shibboleth/attribute-map.xml"/>
        
        <!-- Use a SAML query if no attributes are supplied during SSO. -->
        <AttributeResolver type="Query" subjectMatch="false"/>

        <!-- Default filtering policy for recognized attributes, lets other data pass. -->
        <AttributeFilter type="XML" validate="true" reloadChanges="false" path="/etc/shibboleth/attribute-policy.xml"/>

        <!-- Simple file-based resolver for using a single keypair. -->
        <CredentialResolver type="File" key="/etc/shibboleth/sp-key.pem" certificate="/etc/shibboleth/sp-cert.pem"/>

        <!--
        The default settings can be overridden by creating ApplicationOverride elements (see
        the https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPApplicationOverride topic).
        Resource requests are mapped by web server commands, or the RequestMapper, to an
        applicationId setting.
        
        Example of a second application (for a second vhost) that has a different entityID.
        Resources on the vhost would map to an applicationId of "admin":
        -->
        <!--
        <ApplicationOverride id="admin" entityID="https://admin.example.org/shibboleth"/>
        -->
    </ApplicationDefaults>
    
    <!-- Policies that determine how to process and authenticate runtime messages. -->
    <SecurityPolicyProvider type="XML" validate="true" reloadChanges="false" path="/etc/shibboleth/security-policy.xml"/>

    <!-- Low-level configuration about protocols and bindings available for use. -->
    <ProtocolProvider type="XML" validate="true" reloadChanges="false" path="/etc/shibboleth/protocols.xml"/>

</SPConfig>

sudo wget -nc https://help.switch.ch/aai/docs/shibboleth/SWITCH/2.4/sp/deployment/download/attribute-map.xml \
-P /etc/shibboleth/

sudo wget -nc  https://help.switch.ch/aai/docs/shibboleth/SWITCH/2.4/sp/deployment/download/attribute-policy.xml \
-P /etc/shibboleth/

sudo wget http://ca.aai.switch.ch/SWITCHaaiRootCA.crt.pem -P /etc/shibboleth/

<VirtualHost sp.example.org:443>

...

  Redirect seeother /shibboleth https://sp.example.org/Shibboleth.sso/Metadata

</VirtualHost>

sudo a2ensite default-ssl

sudo a2enmod ssl

sudo /opt/shibboleth-sp/sbin/shibd -t -c /etc/shibboleth/shibboleth2.xml

sudo /etc/init.d/shibd start

sudo apache2ctl configtest
sudo apache2ctl restart 

1. Go to the AAI Resource Registry.
2. Log in with a SWITCHaai or AAI Test account. Use organisation account to get access. In case your organisation doesn't operate yet an AAI Identity Provider, please ask aai@switch.ch for an account.
   SWITCHaai accounts can also be used to manage AAI Test resources but not vice versa.
3. Click on the tab Resources
4. Click on Add a Resource Description
5. Click on Run Shibboleth 2.x wizard
6. Fill out all forms that are marked incomplete. Some forms do not need to be filled out completely.
7. After completing all sections (they should all be marked as 'optional' or 'ok'), click on Submit for Approval.
   A Resource Registration Authority administrator of your organization then has to approve the Resource Description in order to make it active. Only after this step, its description will be included in federation metadata.

<VirtualHost sp.example.org:443>
...

  <Location /secure>

    AuthType shibboleth
    ShibRequireSession On
    require valid-user
  </Location>

</VirtualHost>

sudo apache2ctl restart 

After restarting Apache, try to access: https://sp.example.org/secure/. This directory is protected by Shibboleth in the default configuration. Even if the directory does not exist. When accessing this URL the authentication should be initiated and one should be redirected either to the WAYF or to an Identity Provider.
Upon successful authentication, a HTTP 404 error (File not found) might be returned, because there might be no directory /secure in the web server root directory.
Anyway, if you can access https://sp.example.org/Shibboleth.sso/Session and get back information about the session like the issuer (IdP) and released attributes, this is a good test that the Service Provider was set up successfully.

<html><body><pre>
<?php print_r($_SERVER); ?>
</pre></body></html>

• Have a look at the logfiles. They can be found at the path set in the property log4j.appender.native_log.fileName defined in
  /etc/shibboleth/native.logger and the path log4j.appender.shibd_log.fileName set in
  /etc/shibboleth/shibd.logger for WARN and ERROR messages.
  Most probably /var/log/shibboleth/native.log and /var/log/shibboleth/shibd.log.
• Check /var/log/apache2/error.log and /var/log/apache2/access.log
• Set the log level (log4j.rootCategory) of /etc/shibboleth/native.logger and /etc/shibboleth/shibd.logger to DEBUG.
  Once the problem is solved, don't forget to set it back to WARN or INFO to prevent your log files from growing too big.

No log files are written

Check the permissions of the log files or the path for the log files set in /etc/shibboleth/native.logger or /etc/shibboleth/shibd.logger . If shibd is not run as root user, you might have to adapt the owner of the log directory and files to the user that runs shibd.

No attributes/Certificates problems

Check the Apache SSL certificate with the https://tools.switch.ch/certchaintest/ to make sure the full certificate chain up to the root CA certificate is attached to your certificate.

• https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPSolarisInstall
• https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPSolaris10SourceBuild
• Native SP configuration
• Apache HTTP - General documentation
• Apache HTTP - SSL documentation
• Apache HTTP - Authentication, Authorization and Access Control documentation