SP 3.0.4 IIS module and handlerURL processing

[Michael Brogan]

Sadly, or fortunately, we haven't had a lot of SP3.x uptake yet so it isn't a widespread problem. But it will become one. Thanks for putting a little more urgency on this issue.

--Michael

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Monday, March 25, 2019 1:58 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: SP 3.0.4 IIS module and handlerURL processing

On 3/25/19, 4:42 PM, "users on behalf of Michael Brogan" <users-bounces at shibboleth.net on behalf of mbrogan at uw.edu> wrote:

> My understanding of the work-around from the Jira card is that <ISAPI 
> handlerPrefix=”/path/shibboleth.sso”>  can be used to move the default 
> handler from one path to another. In the case I’m working on, there 
> are multiple application overrides, each with their own handler in the appropriate path. I don’t understand how to apply the work around in that case. Or can “handlerPrefix” also be set within an application override?

No, that's game over, you're correct.

Sigh, I will try and get the fix out at some point soon here, I just really don't have the time to spin up a whole cycle. 
Seeing as it's Windows only, I guess I'll apply executive privilege and ship a 3.0.4.1 to get it out.

-- Scott


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