<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">Am 09.03.2019 um 22:24 schrieb Cantor,
Scott:<br>
</div>
<blockquote type="cite"
cite="mid:19F36BDB-75AB-45B8-814B-1C8DEE91E646@osu.edu">
<pre class="moz-quote-pre" wrap="">why does the SP think, that the request /acs/Shibboleth.sso/SAML2/POST/ is something that it should ignore?
</pre>
<pre class="moz-quote-pre" wrap="">
Don't know. My ability to offer free support no longer extends to these sorts of debugging issues.
My advice is not to use overrides, and you most certainly shouldn't be using them at the path level. This is why.</pre>
</blockquote>
<p>
Thanks for your advice. The use of "overrides" is only a
workaround because the use of the "default" configuration doesn't
work anymore since the upgrade from Shibboleth SP V2.x -->
Shibboleth SP V3.0.3. (see my 1st mail, extract below)<br>
</p>
<p>At this point, the backward compatibility seems to be broken --
or is it just a bug?</p>
<p><span class="tlid-translation translation"><span title=""
class="">I am happy to provide further details and feedback
and are also available for tests to improve Shibboleth.</span></span></p>
<p><span class="tlid-translation translation"><span title=""
class="">/Peter<br>
</span></span></p>
<pre>> I just upgraded my SP (running on IIS WIN2012R) from 2.x to the latest 3.x \
> version.
> So far, everything went well. There's a special request mapping, which worked in \
> 2.x and doesn't in 3.x:
>
> mysp.org/myapp ==> the secured application context
> mysp.org/acs/Shibboleth.sso ==> handlerUrl for ACS</pre>
<blockquote type="cite"
cite="mid:19F36BDB-75AB-45B8-814B-1C8DEE91E646@osu.edu">
</blockquote>
</body>
</html>