This page is under construction
It refers to a product which is still under internal/Alpha test. It will currently slated to ship with V3.0 of the SP
The IISNative DLL is an Shibboleth integration against the API set which was introduced in IIS7. The previous version (isapi_shib.dll) integrated against the old "ISAPI" APIS which in turn required the deployment of explicit down-level support dlls to provide interfaces to the legacy API. The new DLL is a functional super set of isapi_shib plugin, but it does not automatically replace the old one (which is still shipped).
The new DLL takes full advantage of the breadth of the IIS7 APIs. Two notable advantages are
The new plugin is configured using an extension to the existing NativeSPISAPI element (and this documentation will move there). The following changes should be noted
<Site>element is not specified for a site which uses the plugin then the configuration is taken from IIS. Notably the host name is derived from the lower case of the name given to the site.
<Site>element is specified the following extra attributes can be provided:
useVariables=boolean(default true) controls whether attributes are passed the the application as Server Variables.
useHeaders=boolean(default false) controls whether attributes are passed the the application 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.
<Roles>may be specified. This configures the roles that can be used in native Roles-based Authorization. The following elements can be provided:
ShibbolethAuthN). Any principal which is logged in via the Shibboleth SP is given this role.
roleAttributes=space-separated-string-list(no default). All values of all provided attributes with the names given are added to the Roles associated with this principal
<ISAPI normalizeRequest="true" safeHeaderNames="true"> <Roles roleAttributes="ePa ePsa" /> <Site id="1" name="iis.example.org"/> </ISAPI>
The first site will be given the host name
Every SP-authenticated principal will be given the role
ShibUser. Additionally the attributes 'ePa' and 'ePsa' will be queried and their values used as roles. Hence if a user logged in via the SP and the following attributes were provided
The session would be have the REMOTE_USER variable set to be "User" (assuming that the default setting for
ApplicationDefault> were used. and the following roles
ShibbolethAuthN (by Virtue of being "logged in")
The installation is available here
We expect that the next version SP installer will be able to upgrade systems with this overlay installed. But just in case (and for all the other usual good reasons) this installer should not be used on production systems.
For the test release the IIS7Native plugin is installed on top of an existing Shibboleth SP installation. It is expected (but not required) that the installation would have the old style ISAPI plugin configured. You may need/wish to stop IIS during the installation. The installation runs with no dialog and does the following
shibboleth2.xmlto include the new definitions
The installation does not deconfigure the old plugin and you need to do this by hand. Doing this is highly installation dependant (which is why there is no automation) but the following hints may help
Before making any configuration changes to IIS, backup up your system appropriately. Although the overlay installer undoes its own configuration it will not revert any configuration that you change.
%SYSTEMROOT%\System32\InetSrv\config\applicationHost.config and look for the words "shib" or "shib_isapi". The following is the new definition
<globalModules> ... <add name="ShibNative" image="C:\opt\shibboleth-sp\lib64\shibboleth\iis7_shib.dll" /> </globalModules> ... <modules> ... <add name="ShibNative" /> </modules>
In particular the string
isapi_shib.dll indicates that the removal is incomplete. Such entries should be removed,
applicationHost.config file, you may need to inspect the
web.configfiles for the sites and their sub folders.
If the ISAPI module is still configured the following tell-tales will indicate it
An attempt to access a protected resource will return a failure (status 500) and the native log will have the following line
ERROR Shibboleth.NATIVE [<pid>] native_shib: Shibboleth handler invoked at an unconfigured location.
This indicates that configuration for the ISAPI filter is still active somewhere.