Setting up LabTrove as a Shibboleth Service Provider/shibboleth2.xml

From LabTrove Documentation
Revision as of 19:18, 19 December 2012 by DavidNewman (talk)

Jump to: navigation, search
<SPConfig xmlns="urn:mace:shibboleth:2.0:native:sp:config"
    logger="syslog.logger" clockSkew="180">

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

    <!-- The InProcess section contains settings affecting web server modules/filters. -->
    <InProcess logger="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="" scheme="https" port="443"/>

    <!-- Only one listener can be defined, to connect in-process modules to shibd. -->
    <UnixListener address="shibd.sock"/>

    <!-- This set of components stores sessions and other persistent data in daemon memory. -->
    <StorageService type="Memory" id="mem" cleanupInterval="900"/>
    <SessionCache type="StorageService" StorageService="mem" cacheTimeout="3600" inprocTimeout="900" cleanupInterval="900"/>
    <ReplayCache StorageService="mem"/>
    <ArtifactMap artifactTTL="180"/>

    <!-- To customize behavior, map hostnames and path components to applicationId and other settings. -->
    <RequestMapper type="Native">
        <RequestMap applicationId="default">
            The example 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
            <Host name="">
                <Path name="secure" authType="shibboleth" requireSession="true"/>

    The ApplicationDefaults element is where most of Shibboleth's SAML bits are defined.
    Resource requests are mapped by the RequestMapper to an applicationId that
    points into to this section.
    <ApplicationDefaults id="default" policyId="default"
        REMOTE_USER="eppn persistent-id targeted-id">
        <!-- signing="false" encryption="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 can be a relative path, a URL with no hostname (https:///path) or a full URL.
        The system can compute a relative value based on the virtual host. Using handlerSSL="true"
        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"
            handlerURL="/Shibboleth.sso" handlerSSL="false"
            exportLocation="http://localhost/Shibboleth.sso/GetAssertion" exportACL=""
            idpHistory="false" idpHistoryDays="7">

            SessionInitiators handle session requests and relay them to a Discovery page,
            or to an IdP if possible. Automatic session setup will use the default or first
            element (or requireSessionWith can specify a specific id to use).

            <!-- UK-fed the new-style of discovery service. -->
            <SessionInitiator type="Chaining" Location="/DS" id="DS" relayState="cookie">
                <SessionInitiator type="SAML2" acsIndex="1" template="bindingTemplate.html"/>
                <SessionInitiator type="Shib1" acsIndex="5"/>
                <SessionInitiator type="SAMLDS" URL=""/>

            md:AssertionConsumerService locations handle specific SSO protocol bindings,
            such as SAML 2.0 POST or SAML 1.1 Artifact. The isDefault and index attributes
            are used when sessions are initiated to determine how to tell the IdP where and
            how to return the response.
            <md:AssertionConsumerService Location="/SAML2/POST" index="1"
            <md:AssertionConsumerService Location="/SAML2/POST-SimpleSign" index="2"
            <md:AssertionConsumerService Location="/SAML2/Artifact" index="3"
            <md:AssertionConsumerService Location="/SAML2/ECP" index="4"
            <md:AssertionConsumerService Location="/SAML/POST" index="5"
            <md:AssertionConsumerService Location="/SAML/Artifact" index="6"

            <!-- LogoutInitiators enable SP-initiated local or global/single logout of sessions. -->
            <LogoutInitiator type="Chaining" Location="/Logout" relayState="cookie">
                <LogoutInitiator type="SAML2" template="bindingTemplate.html"/>
                <LogoutInitiator type="Local"/>

            <!-- md:SingleLogoutService locations handle single logout (SLO) protocol messages. -->
            <md:SingleLogoutService Location="/SLO/SOAP"
            <md:SingleLogoutService Location="/SLO/Redirect" conf:template="bindingTemplate.html"
            <md:SingleLogoutService Location="/SLO/POST" conf:template="bindingTemplate.html"
            <md:SingleLogoutService Location="/SLO/Artifact" conf:template="bindingTemplate.html"

            <!-- md:ManageNameIDService locations handle NameID management (NIM) protocol messages. -->
            <md:ManageNameIDService Location="/NIM/SOAP"
            <md:ManageNameIDService Location="/NIM/Redirect" conf:template="bindingTemplate.html"
            <md:ManageNameIDService Location="/NIM/POST" conf:template="bindingTemplate.html"
            <md:ManageNameIDService Location="/NIM/Artifact" conf:template="bindingTemplate.html"

            md:ArtifactResolutionService locations resolve artifacts issued when using the
            SAML 2.0 HTTP-Artifact binding on outgoing messages, generally uses SOAP.
            <md:ArtifactResolutionService Location="/Artifact/SOAP" index="1"

            <!-- Extension service that generates "approximate" metadata based on SP configuration. -->
            <Handler type="MetadataGenerator" Location="/Metadata" signing="false"/>

            <!-- Status reporting service. -->
            <Handler type="Status" Location="/Status" acl=""/>

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


        Allows overriding of error template filenames. You can also add attributes with values
        that can be plugged into the templates.
        <Errors supportContact=""

        <!-- Uncomment and modify to tweak settings for specific IdPs or groups. -->
        <!-- <RelyingParty Name="SpecialFederation" keyName="SpecialKey"/> -->

        <!-- Chains together all your metadata sources. -->
        <MetadataProvider type="Chaining">

            <!-- UK-fed metadata provider -->
            <MetadataProvider type="XML" uri=""
                 backingFilePath="/var/opt/shibboleth/ukfederation-metadata.xml" reloadInterval="14400">
               <MetadataFilter type="RequireValidUntil" maxValidityInterval="2592000"/>
               <MetadataFilter type="Signature" certificate="ukfederation.pem"/>


        <!-- Chain the two built-in trust engines together. -->
        <TrustEngine type="Chaining">
            <TrustEngine type="ExplicitKey"/>
            <TrustEngine type="PKIX"/>

        <!-- Map to extract attributes from SAML assertions. -->
        <AttributeExtractor type="XML" validate="true" path="attribute-map.xml"/>

        <!-- Use a SAML query if no attributes are supplied during SSO. -->
        <AttributeResolver type="Query" subjectMatch="true"/>

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

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


    <!-- Each policy defines a set of rules to use to secure messages. -->
        The predefined policy enforces replay/freshness, standard
        condition processing, and permits signing and client TLS.
        <Policy id="default" validate="false">
            <PolicyRule type="MessageFlow" checkReplay="true" expires="60"/>
            <PolicyRule type="Conditions">
                <PolicyRule type="Audience"/>
            <PolicyRule type="ClientCertAuth" errorFatal="true"/>
            <PolicyRule type="XMLSigning" errorFatal="true"/>
            <PolicyRule type="SimpleSigning" errorFatal="true"/>