-<SPConfig xmlns="urn:mace:shibboleth:2.0:native:sp:config"\r
- xmlns:conf="urn:mace:shibboleth:2.0:native:sp:config"\r
- xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"\r
- xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" \r
- xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"\r
- clockSkew="180">\r
-\r
- <!--\r
- The InProcess section contains settings affecting web server modules.\r
- Required for IIS, but can be removed when using other web servers.\r
- -->\r
- <InProcess logger="native.logger">\r
- <ISAPI normalizeRequest="true" safeHeaderNames="true">\r
- <!--\r
- Maps IIS Instance ID values to the host scheme/name/port. The name is\r
- required so that the proper <Host> in the request map above is found without\r
- having to cover every possible DNS/IP combination the user might enter.\r
- -->\r
- <Site id="1" name="sp.example.org"/>\r
- <!--\r
- When the port and scheme are omitted, the HTTP request's port and scheme are used.\r
- If these are wrong because of virtualization, they can be explicitly set here to\r
- ensure proper redirect generation.\r
- -->\r
- <!--\r
- <Site id="42" name="virtual.example.org" scheme="https" port="443"/>\r
- -->\r
- </ISAPI>\r
- </InProcess>\r
-\r
- <!--\r
- By default, in-memory StorageService, ReplayCache, ArtifactMap, and SessionCache\r
- are used. See example-shibboleth2.xml for samples of explicitly configuring them.\r
- -->\r
-\r
- <!--\r
- To customize behavior for specific resources on IIS, and to link vhosts or\r
- resources to ApplicationOverride settings below, use the XML syntax below.\r
- See https://spaces.internet2.edu/display/SHIB2/NativeSPRequestMapHowTo for help.\r
- \r
- Apache users should rely on web server options/commands in most cases, and can remove the\r
- RequestMapper element. See https://spaces.internet2.edu/display/SHIB2/NativeSPApacheConfig\r
- -->\r
- <RequestMapper type="Native">\r
- <RequestMap>\r
- <!--\r
- The example requires a session for documents in /secure on the containing host with http and\r
- https on the default ports. Note that the name and port in the <Host> elements MUST match\r
- Apache's ServerName and Port directives or the IIS Site name in the <ISAPI> element above.\r
- -->\r
- <Host name="sp.example.org">\r
- <Path name="secure" authType="shibboleth" requireSession="true"/>\r
- </Host>\r
- <!-- Example of a second vhost mapped to a different applicationId. -->\r
- <!--\r
- <Host name="admin.example.org" applicationId="admin" authType="shibboleth" requireSession="true"/>\r
- -->\r
- </RequestMap>\r
- </RequestMapper>\r
-\r
- <!--\r
- The ApplicationDefaults element is where most of Shibboleth's SAML bits are defined.\r
- Resource requests are mapped by the RequestMapper to an applicationId that\r
- points into to this section (or to the defaults here).\r
- -->\r
- <ApplicationDefaults entityID="https://sp.example.org/shibboleth"\r
- REMOTE_USER="eppn persistent-id targeted-id">\r
-\r
- <!--\r
- Controls session lifetimes, address checks, cookie handling, and the protocol handlers.\r
- You MUST supply an effectively unique handlerURL value for each of your applications.\r
- The value defaults to /Shibboleth.sso, and should be a relative path, with the SP computing\r
- a relative value based on the virtual host. Using handlerSSL="true", the default, will force\r
- the protocol to be https. You should also add a cookieProps setting of "; path=/; secure"\r
- in that case. Note that while we default checkAddress to "false", this has a negative\r
- impact on the security of the SP. Stealing cookies/sessions is much easier with this disabled.\r
- -->\r
- <Sessions lifetime="28800" timeout="3600" checkAddress="false" relayState="ss:mem" handlerSSL="false">\r
-\r
- <!--\r
- Configures SSO for a default IdP. To allow for >1 IdP, remove\r
- entityID property and adjust discoveryURL to point to discovery service.\r
- (Set discoveryProtocol to "WAYF" for legacy Shibboleth WAYF support.)\r
- You can also override entityID on /Login query string, or in RequestMap/htaccess.\r
- -->\r
- <SSO entityID="https://idp.example.org/shibboleth"\r
- discoveryProtocol="SAMLDS" discoveryURL="https://ds.example.org/DS/WAYF">\r
- SAML2 SAML1\r
- </SSO>\r
-\r
- <!-- SAML and local-only logout. -->\r
- <Logout>SAML2 Local</Logout>\r
-\r
- <!-- Extension service that generates "approximate" metadata based on SP configuration. -->\r
- <Handler type="MetadataGenerator" Location="/Metadata" signing="false"/>\r
-\r
- <!-- Status reporting service. -->\r
- <Handler type="Status" Location="/Status" acl="127.0.0.1"/>\r
-\r
- <!-- Session diagnostic service. -->\r
- <Handler type="Session" Location="/Session" showAttributeValues="false"/>\r
-\r
- <!-- JSON feed of discovery information. -->\r
- <Handler type="DiscoveryFeed" Location="/DiscoFeed"/>\r
- </Sessions>\r
-\r
- <!--\r
- Allows overriding of error template information/filenames. You can\r
- also add attributes with values that can be plugged into the templates.\r
- -->\r
- <Errors supportContact="root@localhost"\r
- logoLocation="/shibboleth-sp/logo.jpg"\r
- styleSheet="/shibboleth-sp/main.css"/>\r
- \r
- <!-- Example of remotely supplied batch of signed metadata. -->\r
- <!--\r
- <MetadataProvider type="XML" uri="http://federation.org/federation-metadata.xml"\r
- backingFilePath="federation-metadata.xml" reloadInterval="7200">\r
- <MetadataFilter type="RequireValidUntil" maxValidityInterval="2419200"/>\r
- <MetadataFilter type="Signature" certificate="fedsigner.pem"/>\r
- </MetadataProvider>\r
- -->\r
-\r
- <!-- Example of locally maintained metadata. -->\r
- <!--\r
- <MetadataProvider type="XML" file="partner-metadata.xml"/>\r
- -->\r
-\r
- <!-- Map to extract attributes from SAML assertions. -->\r
- <AttributeExtractor type="XML" validate="true" path="attribute-map.xml"/>\r
- \r
- <!-- Use a SAML query if no attributes are supplied during SSO. -->\r
- <AttributeResolver type="Query" subjectMatch="true"/>\r
-\r
- <!-- Default filtering policy for recognized attributes, lets other data pass. -->\r
- <AttributeFilter type="XML" validate="true" path="attribute-policy.xml"/>\r
-\r
- <!-- Simple file-based resolver for using a single keypair. -->\r
- <CredentialResolver type="File" key="sp-key.pem" certificate="sp-cert.pem"/>\r
-\r
- <!--\r
- The default settings can be overridden by creating ApplicationOverride elements (see\r
- the https://spaces.internet2.edu/display/SHIB2/NativeSPApplicationOverride topic).\r
- Resource requests are mapped by web server commands, or the RequestMapper, to an\r
- applicationId setting.\r
- \r
- Example of a second application (for a second vhost) that has a different entityID.\r
- Resources on the vhost would map to an applicationId of "admin":\r
- -->\r
- <!--\r
- <ApplicationOverride id="admin" entityID="https://admin.example.org/shibboleth"/>\r
- -->\r
- </ApplicationDefaults>\r
- \r
- <!-- Policies that determine how to process and authenticate runtime messages. -->\r
- <SecurityPolicyProvider type="XML" validate="true" path="security-policy.xml"/>\r
-\r
- <!-- Low-level configuration about protocols and bindings available for use. -->\r
- <ProtocolProvider type="XML" validate="true" reloadChanges="false" path="protocols.xml"/>\r
-\r
-</SPConfig>\r
+<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">
+
+ <!--
+ 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="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>
+
+ <!--
+ By default, in-memory StorageService, ReplayCache, ArtifactMap, and SessionCache
+ are used. See example-shibboleth2.xml for samples of explicitly configuring them.
+ -->
+
+ <!--
+ To customize behavior for specific resources on IIS, and to link vhosts or
+ resources to ApplicationOverride settings below, use the XML syntax below.
+ See https://spaces.internet2.edu/display/SHIB2/NativeSPRequestMapHowTo for help.
+
+ Apache users should rely on web server options/commands in most cases, and can remove the
+ RequestMapper element. See https://spaces.internet2.edu/display/SHIB2/NativeSPApacheConfig
+ -->
+ <RequestMapper type="Native">
+ <RequestMap>
+ <!--
+ 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="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 (or to the defaults here).
+ -->
+ <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.
+ 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" relayState="ss:mem" handlerSSL="false">
+
+ <!--
+ Configures SSO for a default IdP. To allow for >1 IdP, remove
+ entityID property and adjust discoveryURL to point to discovery service.
+ (Set discoveryProtocol to "WAYF" for legacy Shibboleth WAYF support.)
+ You can also override entityID on /Login query string, or in RequestMap/htaccess.
+ -->
+ <SSO entityID="https://idp.example.org/shibboleth"
+ discoveryProtocol="SAMLDS" discoveryURL="https://ds.example.org/DS/WAYF">
+ SAML2 SAML1
+ </SSO>
+
+ <!-- SAML and local-only logout. -->
+ <Logout>SAML2 Local</Logout>
+
+ <!-- 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="127.0.0.1"/>
+
+ <!-- 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="root@localhost"
+ logoLocation="/shibboleth-sp/logo.jpg"
+ styleSheet="/shibboleth-sp/main.css"/>
+
+ <!-- Example of remotely supplied batch of signed metadata. -->
+ <!--
+ <MetadataProvider type="XML" uri="http://federation.org/federation-metadata.xml"
+ backingFilePath="federation-metadata.xml" reloadInterval="7200">
+ <MetadataFilter type="RequireValidUntil" maxValidityInterval="2419200"/>
+ <MetadataFilter type="Signature" certificate="fedsigner.pem"/>
+ </MetadataProvider>
+ -->
+
+ <!-- Example of locally maintained metadata. -->
+ <!--
+ <MetadataProvider type="XML" file="partner-metadata.xml"/>
+ -->
+
+ <!-- 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"/>
+
+ <!--
+ 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":
+ -->
+ <!--
+ <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"/>
+
+ <!-- Low-level configuration about protocols and bindings available for use. -->
+ <ProtocolProvider type="XML" validate="true" reloadChanges="false" path="protocols.xml"/>
+
+</SPConfig>
projects / shibboleth / cpp-sp.git / blobdiff