Once you get that green arrow, the rest is going to be SP configuration work.
Check Application Pool 32-bit Application Support
If you are using the 32-bit library on 64-bit Windows, you'll need to activate support for 32-bit applications. In the Application Pools list, select the application pool for your site(s), and view Advanced Settings. In the (General) group, set "Enable 32-Bit Applications" to True.
Site and Request Mapping
The first thing to check is for the proper
<Site> elements defined in the
<ISAPI> configuration element. You MUST create them for each web site you're using the filter with by mapping from the IIS Site Instance ID to the right hostname(s). You can find the ID on the GUI in the list of Web Sites. It's often a large number on IIS 6.
Apache is much simpler when it comes to getting at least initial interception to function, but it depends on how you choose to configure it. If you use .htaccess files, things are pretty automatic, you just have to do:
AuthType shibboleth ShibRequestSetting requireSession 1 require valid-user
If you're relying on the
<RequestMapper> instead, then you'll run into issues based on server name configuration details. The Apache
ServerName command MUST be set to match what you put in the map's
<Host> element and you'll need to make sure
UseCanonicalName On is set. But additionally you'll need to get the module running for those requests by globally activating the module for those resources, using this kind of approach:
<Location /> AuthType shibboleth require shibboleth </Location>