Overview
The <RequestMapper> element configures the component used by the SP to map incoming requests to the set of configuration options that should be applied to them. You can think of it as a portable equivalent of the Apache <Location> feature, which associates Apache directives with specific portions of URLs. Like that feature, the request mapper operates based on URL, not on the physical path paths of the underlying files, if any.
Another critical role of the request mapper is to map each request to the appropriate Shibboleth application, thereby connecting the resource-oriented settings to the more general behavior defined per-application as a unit.
For a general overview with examples, see the request mapper HOWTO page.
While Apache-based deployments can, and usually should, rely entirely on Apache's functionality for this purposefunction, IIS provides no such capability. The request mapper allows the SP to insulate itself from the differences between servers.
Omitting this element will result in a "Native" plugin type with an empty/default configuration. This empty configuration maps all requests to default application settings the settings in the <ApplicationDefaults> section of the configuration, and adds no other settings, unless overridden by web server-specific options.The RequestMapper is a Reloadable XML File.
Types
Two different type types of Request Mapper are available:
Type | Function |
|---|---|
| Native | A |
| plugin that integrates with the native web server |
| 's configuration capabilities |
An internal (to the SP) request mapper.
Attributes and Child Elements
These are detailed in for each Mapper type.
...
A plugin that solely relies on the XML configuration within the SP itself |
Reference
Common Attributes
All <RequestMapper> plugins support the following attributes:
| Name | Type | Required? | Description |
|---|---|---|---|
| string | Y | Specifies the type of RequestMapper plugin to use |