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"
- logger="syslog.logger" clockSkew="180">
+ clockSkew="180">
- <!-- The OutOfProcess section contains properties affecting the shibd daemon. -->
- <OutOfProcess logger="shibd.logger">
- <!--
- <Extensions>
- <Library path="odbc-store.so" fatal="true"/>
- </Extensions>
- -->
- </OutOfProcess>
-
- <!-- The InProcess section conrains 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="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>
-
- <!-- Only one listener can be defined, to connect in-process modules to shibd. -->
- <UnixListener address="shibd.sock"/>
- <!-- <TCPListener address="127.0.0.1" port="12345" acl="127.0.0.1"/> -->
-
- <!-- 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"/>
-
- <!-- This set of components stores sessions and other persistent data in an ODBC database. -->
<!--
- <StorageService type="ODBC" id="db" cleanupInterval="900">
- <ConnectionString>
- DRIVER=drivername;SERVER=dbserver;UID=shibboleth;PWD=password;DATABASE=shibboleth;APP=Shibboleth
- </ConnectionString>
- </StorageService>
- <SessionCache type="StorageService" StorageService="db" cacheTimeout="3600" inprocTimeout="900" cleanupInterval="900"/>
- <ReplayCache StorageService="db"/>
- <ArtifactMap StorageService="db" artifactTTL="180"/>
+ By default, in-memory StorageService, ReplayCache, ArtifactMap, and SessionCache
+ are used. See example-shibboleth2.xml for samples of explicitly configuring them.
-->
- <!-- 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
- below.
- -->
- <Host name="sp.example.org">
- <Path name="secure" authType="shibboleth" requireSession="true"/>
- </Host>
- <!-- Example of a second vhost mapped to a different applicationId. -->
- <!--
- <Host name="admin.example.org" applicationId="admin" authType="shibboleth" requireSession="true"/>
- -->
- </RequestMap>
- </RequestMapper>
-
<!--
- 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.
+ 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://spaces.internet2.edu/display/SHIB2/NativeSPConfigurationElements for help.
+
+ For examples with the RequestMap XML syntax instead, see the example-shibboleth2.xml
+ file, and the https://spaces.internet2.edu/display/SHIB2/NativeSPRequestMapHowTo topic.
-->
- <ApplicationDefaults id="default" policyId="default"
- entityID="https://sp.example.org/shibboleth"
- REMOTE_USER="eppn persistent-id targeted-id"
- signing="false" encryption="false">
+
+ <!-- The ApplicationDefaults element is where most of Shibboleth's SAML bits are defined. -->
+ <ApplicationDefaults entityID="https://sp.example.org/shibboleth"
+ REMOTE_USER="eppn persistent-id targeted-id">
<!--
Controls session lifetimes, address checks, cookie handling, and the protocol handlers.
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="127.0.0.1"
- idpHistory="false" idpHistoryDays="7">
+ handlerURL="/Shibboleth.sso" handlerSSL="false">
<!--
SessionInitiators handle session requests and relay them to a Discovery page,
element (or requireSessionWith can specify a specific id to use).
-->
- <!-- Default example directs to a specific IdP's SSO service (favoring SAML 2 over Shib 1). -->
- <SessionInitiator type="Chaining" Location="/Login" isDefault="true" id="Intranet"
- relayState="cookie" entityID="https://idp.example.org/shibboleth">
- <SessionInitiator type="SAML2" acsIndex="1" template="bindingTemplate.html"/>
- <SessionInitiator type="Shib1" acsIndex="5"/>
- </SessionInitiator>
-
- <!-- An example using an old-style WAYF, which means Shib 1 only unless an entityID is provided. -->
- <SessionInitiator type="Chaining" Location="/WAYF" id="WAYF" relayState="cookie">
- <SessionInitiator type="SAML2" acsIndex="1" template="bindingTemplate.html"/>
- <SessionInitiator type="Shib1" acsIndex="5"/>
- <SessionInitiator type="WAYF" acsIndex="5" URL="https://wayf.example.org/WAYF"/>
- </SessionInitiator>
-
- <!-- An example supporting the new-style of discovery service. -->
- <SessionInitiator type="Chaining" Location="/DS" id="DS" relayState="cookie">
+ <!-- Default directs to a specific IdP (favoring SAML 2 over Shib 1). -->
+ <SessionInitiator type="Chaining" Location="/Login" isDefault="true" id="Login"
+ relayState="cookie" entityID="https://idp.example.org/shibboleth">
+
<SessionInitiator type="SAML2" acsIndex="1" template="bindingTemplate.html"/>
<SessionInitiator type="Shib1" acsIndex="5"/>
+ <!--
+ 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="https://ds.example.org/DS/WAYF"/>
+ <SessionInitiator type="WAYF" acsIndex="5" URL="https://wayf.example.org/WAYF"/>
+ -->
</SessionInitiator>
<!--
</Sessions>
<!--
- You should customize these pages! You can add attributes with values that can be plugged
- into your templates. You can remove the access attribute to cause the module to return a
- standard 403 Forbidden error code if authorization fails, and then customize that condition
- using your web server.
+ Allows overriding of error template filenames. You can also add attributes with values
+ that can be plugged into the templates.
-->
- <Errors session="sessionError.html"
- metadata="metadataError.html"
- access="accessError.html"
- ssl="sslError.html"
- localLogout="localLogout.html"
- globalLogout="globalLogout.html"
- supportContact="root@localhost"
+ <Errors supportContact="root@localhost"
logoLocation="/shibboleth-sp/logo.jpg"
styleSheet="/shibboleth-sp/main.css"/>
- <!-- 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">
<!-- Example of remotely supplied batch of signed metadata. -->
-->
</MetadataProvider>
- <!-- Chain the two built-in trust engines together. -->
- <TrustEngine type="Chaining">
- <TrustEngine type="ExplicitKey"/>
- <TrustEngine type="PKIX"/>
- </TrustEngine>
-
<!-- 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"/>
+ <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"/>
- <!-- Example of a second application (using a second vhost) that has a different entityID. -->
- <!-- <ApplicationOverride id="admin" entityID="https://admin.example.org/shibboleth"/> -->
-
- </ApplicationDefaults>
-
- <!-- Each policy defines a set of rules to use to secure messages. -->
- <SecurityPolicies>
<!--
- The predefined policy enforces replay/freshness, standard
- condition processing, and permits signing and client TLS.
+ The default settings can be overridden by creating ApplicationOverride elements (see
+ the https://spaces.internet2.edu/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":
-->
- <Policy id="default" validate="false">
- <PolicyRule type="MessageFlow" checkReplay="true" expires="60"/>
- <PolicyRule type="Conditions">
- <PolicyRule type="Audience"/>
- <!-- Enable Delegation rule to permit delegated access. -->
- <!-- <PolicyRule type="Delegation"/> -->
- </PolicyRule>
- <PolicyRule type="ClientCertAuth" errorFatal="true"/>
- <PolicyRule type="XMLSigning" errorFatal="true"/>
- <PolicyRule type="SimpleSigning" errorFatal="true"/>
- </Policy>
- </SecurityPolicies>
+ <!--
+ <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" path="security-policy.xml"/>
</SPConfig>
projects / shibboleth / sp.git / blobdiff