View Source

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.

Background

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"?

IIS7

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.