ISAPI Filter Won't Protect One Site

[Kim, Allan]

Two possible "something elses" for IIS are:

"Invoke handler only if request is mapped to..." and "runAllManagedModulesForAllRequests"

(I'm not particularly good at IIS either. Unfortunately no one else will admit to any IIS skills.)

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Klingenstein, Nate
Sent: Monday, April 9, 2018 12:37 PM
To: Shib Users <users at shibboleth.net>
Subject: ISAPI Filter Won't Protect One Site

All,

I'm bad at IIS.  Please forgive.

We have a basic SP configuration that protects 2 Sites.  Requests to protected locations on the first Site work fine.  Requests to the other site are never protected.

I've checked the Site mappings many times.  I've made sure the filter is present and enabled for that Site.  Everything worked in dev and stage with apparently identical configuration(beyond hostnames and site ID's).  Everything works if I access the content on the main Site.

Other people get to touch this IIS configuration.  I'm fairly sure the Shibboleth configuration is right.

I have no answer beyond that "something else" in IIS is preventing the filter from working on that Site.

Does anyone have any ideas?  Thanks in advance, Nate.
--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net