The <ISAPI> element defines the integration of Shibboleth with IIS.
In SP V3, this is achieved using the "new" since IIS7 interface. This has significant benefits as detailed elsewhere, and also means that less configuration may be needed.
Restart IIS after making changes
You'll need to restart IIS after changing this particular set of options.
Existing installations will continue to use the old ISAPI based as documented here. If you convert an existing site to use the new plugin (as described here) you should be aware that although the configuration is compatible, some defaults have changed and you will need to make changes to your applications to take advantage of the new plugin.
Attributes
| Name | Type | Default | Description |
|---|---|---|---|
normalizeRequest | boolean | true | To be Deprecated |
safeHeaderNames | boolean | TBD | Causes all non-alphanumeric characters to be automatically removed from the names of all SP-controlled {{headers. |
useVariables | boolean | true | Controls whether attributes are passed the the application as Server Variables. |
useHeaders | boolean | false | Controls whether attributes are passed as HTTP Headers. This setting should be avoided, but is present to provide a level of compatibility with applications developed against the old isapi_shib plugin. |
Child Elements
| Element | Cardinalty | Description |
|---|---|---|
<Site> | 0 or more | Controls how Shibboleth perceives each IIS site |
<Roles> | 0 or 1 | Provides support for roles based authorization |