NativeSPRequestMap

The Shibboleth V2 IdP and SP software have reached End of Life and are no longer supported. This documentation is available for historical purposes only. See the IDP v4 and SP v3 wiki spaces for current documentation on the supported versions.

NativeSPRequestMap

The <RequestMap> element is the root of the XML-based request mapper configuration.

<RequestMap applicationId="default"> <Host name="www.example.org"> <Path name="secure" authType="shibboleth" requireSession="true"/> </Host> <Host name="admin.example.org" applicationId="admin" authType="shibboleth" requireSession="true"> <AccessControl> <Rule require="affiliation">faculty@osu.edu student@osu.edu</Rule> </AccessControl> </Host> </RequestMap>

Attributes

Content Specifiers

The root element applies to all requests, so has no attributes to limit matching behavior.

Content Settings

XML attributes corresponding to request mapper properties are used.

A special requirement of this root element is that it MUST contain an applicationId attribute with a value of "default", which in turn matches the required id attribute of the outer-most <ApplicationDefaults> element in the shibboleth2.xml file.

Child Elements

Access Control

Nested Content Specifiers

Zero or more of these "overrides" to match specific virtual hosts can be included.

  • <Host>

    • Matches requests with the exact hostname (and optionally port and scheme).

  • <HostRegex>

    • Matches requests with a URL prefix matching a regular expression. The prefix contains everyting up until the slash following the hostname or port.

Matching is done by examining <Host> elements in order, and then checking any <HostRegex> elements in order.

For more details on how the request mapping process works, see the request mapper HOWTO.