Config of Shibboleth - Debug Question

Joseph Corso jcorso at
Wed Nov 12 12:32:12 EST 2014

Thank you! 1 step Closer. Service is started. At this point, I only Identified the sp and idp fqdns in the file. And the fed metadata location.

So... closer, but still not there...

Here is the current file. Status page does not open.

<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">
            <Library path="" fatal="true"/>

    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="shib.campuscafesoftware.local"/>
            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="" scheme="https" port="443"/>

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

    <!-- 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" cacheAssertions="false"
                  cacheAllowance="900" inprocTimeout="900" cleanupInterval="900"/>
    <ReplayCache StorageService="mem"/>
    <ArtifactMap artifactTTL="180"/>

    <!-- This set of components stores sessions and other persistent data in an ODBC database. -->
    <StorageService type="ODBC" id="db" cleanupInterval="900">
    <SessionCache type="StorageService" StorageService="db" cacheAssertions="false"
                  cacheTimeout="3600" inprocTimeout="900" cleanupInterval="900"/>
    <ReplayCache StorageService="db"/>
    <ArtifactMap StorageService="db" artifactTTL="180"/>

    To customize behavior for specific resources on Apache, and to link vhosts or
    resources to ApplicationOverride settings below, use web server options/commands.
    See for help.

    For examples with the RequestMap XML syntax instead, see the example-shibboleth2.xml
    file, and the topic.
    <RequestMapper type="Native">
            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 above.
            <Host name="shib.campuscafesoftware.local">
                <Path name="secure" authType="shibboleth" requireSession="true"/>
            <!-- Example of a second vhost mapped to a different applicationId. -->
            <Host name="" applicationId="admin" 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 (or to the defaults here).
    <ApplicationDefaults entityID="https://shib.campuscafesoftware.local/shibboleth"
                         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 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 set cookieProps to "https" for SSL-only sites.
        Note that while we default checkAddress to "false", this has a negative impact on the
        security of your site. Stealing sessions via cookie theft is much easier with this disabled.
        <Sessions lifetime="28800" timeout="3600" checkAddress="false"
            handlerURL="/Shibboleth.sso" handlerSSL="false" cookieProps="http" relayState="ss:mem"
            exportLocation="http://localhost/Shibboleth.sso/GetAssertion" exportACL=""
            idpHistory="false" idpHistoryDays="7">

            The "stripped down" files use the shorthand syntax for configuring handlers.
            This uses the old "every handler specified directly" syntax. You can replace
            or supplement the new syntax following these examples.

            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).

            <!-- Default directs to a specific IdP (favoring SAML 2 over Shib 1). -->
            <SessionInitiator type="Chaining" Location="/Login" isDefault="true" id="Login"

                <SessionInitiator type="SAML2" template="bindingTemplate.html"/>
                <SessionInitiator type="Shib1"/>
                To allow for >1 IdP, remove entityID property from Chaining element and add
                *either* of the SAMLDS or WAYF handlers below:

                <SessionInitiator type="SAMLDS" URL=""/>
                <SessionInitiator type="WAYF" 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">
                <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=" ::1"/>

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

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

            <!-- Checks for required attribute(s) before login completes. -->
            <Handler type="AttributeChecker" Location="/AttrChecker" template="attrChecker.html"
                attributes="eppn" flushSession="true"/>

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

        Uncomment and modify to tweak settings for specific IdPs or groups. Settings here
        generally match those allowed by the <ApplicationDefaults> element.
        <RelyingParty Name="SpecialFederation" keyName="SpecialKey"/>

        <!-- Example of remotely supplied batch of signed metadata. -->
        <MetadataProvider type="XML" uri=""
              backingFilePath="federation-metadata.xml" reloadInterval="7200">
            <MetadataFilter type="RequireValidUntil" maxValidityInterval="2419200"/>
            <MetadataFilter type="Signature" certificate="fedsigner.pem"/>

        <!-- Example of locally maintained metadata. -->
        <MetadataProvider type="XML" file="partner-metadata.xml"/>

        <!-- TrustEngines run in order to evaluate peer keys and certificates. -->
        <TrustEngine type="ExplicitKey"/>
        <TrustEngine type="PKIX"/>

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

        <!-- Extracts support information for IdP from its metadata. -->
        <AttributeExtractor type="Metadata" errorURL="errorURL" DisplayName="displayName"/>

        <!-- 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"/>

        The default settings can be overridden by creating ApplicationOverride elements (see
        the 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=""/>

    <!-- Policies that determine how to process and authenticate runtime messages. -->
    <SecurityPolicyProvider type="XML" validate="true" path="security-policy.xml"/>

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


Joseph Corso

-----Original Message-----
From: users-bounces at [mailto:users-bounces at] On Behalf Of Peter Schober
Sent: Wednesday, November 12, 2014 12:23 PM
To: users at
Subject: Re: Config of Shibboleth - Debug Question

* Joseph Corso <jcorso at> [2014-11-12 18:06]:
> I have a sample shibboleth file in the folder with shibboleth2. Can I
> use that and start there again? Do you have a better recommendation?

Start with the pristine copy (of shibboleth2.xml) the software installs into the "dist" directory for that very purpose (on MS-Windows; on Unixen the files are sufficed with ".dist"), -peter
To unsubscribe from this list send an email to users-unsubscribe at

More information about the users mailing list