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.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

IIS7 and later only

This page is based on a "nature study" of working IIS/ISAPI configuration. It should not be considered as definitive guidance, rather as a hint for configuration and pointers towards further research.

The way in which IIS was configured changed fundamentally in II7 and this document reflects only these later versions.


The Shibboleth IIS integration consists of two parts and ISAPI filter and an ISAPI Handler map. The latter deals with the Shibboleth end points under {{\Shibboleth.sso\}} and the former with 'all the rest'.  The Shibboleth installer uses a small script in visual basic to configure the module, this calls legacy (IIS6 and earlier) WMI APIs and these APIs are often missing in more modern installations.  This results in a successful installation, but with the message {{Could not locate IIS adaptor}} in the log.

This page is intended to answer the question "What next"?


AFAICS, the basis of IIS7 configuration is a cascade of xml files.  

  • At the "bottom of the stack", the are files in C:\Windows\System32\inetsrv\config\ with the most notable being applicationHost.config which define global settings and defaults.
  • For each website or virtual folder there is a file {{web.config}} which over rides and settings below it in the stack.

  • No labels