ISAPI extension can only be invoked to process Shibboleth

[Fournier, Danny G]

> Date: Wed, 24 Jun 2015 20:04:27 +0000
> From: "Cantor, Scott" <cantor.2 at osu.edu>
> To: Shib Users <users at shibboleth.net>
> Subject: Re: ISAPI extension can only be invoked to process Shibboleth
> 	protocol requests
> Message-ID: <C71D1814-C6CA-42A5-B031-8EE27789FD1A at osu.edu>
> Content-Type: text/plain; charset="utf-8"
> 
> On 6/24/15, 3:40 PM, "users on behalf of Fournier, Danny G" <users-
> bounces at shibboleth.net on behalf of Danny.Fournier at dfo-mpo.gc.ca> wrote:
> 
> >
> ><Host name="my.domain.com" scheme="https" port="443">
> >                <Path name="abc" requireSession="false">
> >
> >                                <PathRegex regex=".*" authType="shibboleth"
> >                                                requireSession="true"
> > requireSessionWith="Internet" applicationId="xyz" />
> 
> You're mapping what's below /abc to that applicationId, but you haven't put the
> handlerURL there, so it's not going to map to that applicationId. Basic mistake.

Solution is right here! I was sure I had tried prefixing the mapping with /abc though.

Sickening when I think that I've been configuring our service providers for all this time and never noticed or faced this issue before. 

I wasn't aware that you couldn't map two different paths like that. Thanks!
 
> -- Scott