<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="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="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=""/>
            <!--
            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="">
                <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=""
                         homeURL=""
                         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-test.switch.ch/aaitest/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=""
            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.aaitest.xml"
            backingFilePath="metadata..xml"
            reloadInterval="3600">
            <MetadataFilter type="RequireValidUntil" maxValidityInterval="604800"/>
            <MetadataFilter type="Signature" verifyName="false">
                <TrustEngine type="StaticPKIX"
                    certificate="SWITCHaaiRootCA.crt.pem"
                    verifyDepth="2" checkRevocation="fullChain"/>
            </MetadataFilter>
        </MetadataProvider>

        <!-- Map to extract attributes from SAML assertions. -->
        <AttributeExtractor type="XML" validate="true" reloadChanges="false" path="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="attribute-policy.xml"/>

        <!-- Simple file-based resolver for using a single keypair. -->
        <CredentialResolver type="File" key="" certificate=""/>

        <!--
        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="security-policy.xml"/>

    <!-- Low-level configuration about protocols and bindings available for use. -->
    <ProtocolProvider type="XML" validate="true" reloadChanges="false" path="protocols.xml"/>

</SPConfig>
