SP V3 handlerUrl="/myapppath/Schibboleth.sso" leads to 404

[Peter Egli]

thanks for the answers.
The request/communication looks like this:

HTTP GET :https://mysp.org/myapp <redirect to idp, with correct authn request + 
login at idp, idp returns an assertion to the acs:> HTTP POST: 
https://mysp.org/acs/Shibboleth.sso/SAML2/POST and the answer is:
*HTTP/1.1 404 Not Found **Content-Type*: text/html *Server*: 
Microsoft-IIS/8.5 *X-Powered-By*: ASP.NET *Date*: Sat, 09 Mar 2019 
09:06:26 GMT *Content-Length*: 1245
Here are the configuration snippets:      <RequestMapper type="Native">
             <RequestMap encoding="URL" applicationId="default">
             <Host scheme="https" name="mysp.org" port="443">
                 <Path name="*myapp*" authType="shibboleth" requireSession="true"*applicationId="spacs"*  />
                 <Path name=*"acs/Shibboleth.sso"*  *applicationId="spacs"*  />
                 <Path name="secure" authType="shibboleth" requireSession="true" />
             </Host>
         </RequestMap>
     </RequestMapper>

     <ApplicationOverride*id="spacs"*  entityID="urn:eiam.admin.ch:pep:testpep">
         <Sessions lifetime="28800" timeout="3600"
                   checkAddress="false"
                   *handlerURL="/acs/Shibboleth.sso"*  >
	    <SSO entityID="urn:myidp.org:idp:testidp">SAML2</SSO>
             <Logout>SAML2 Local</Logout>
             <LogoutInitiator type="Admin" Location="/Logout/Admin" acl="10.0.8.93 ::1" />
             <Handler type="MetadataGenerator" Location="/Metadata" signing="false"/>
             <Handler type="Status" Location="/Status"/>
             <Handler type="Session" Location="/Session" showAttributeValues="true"/>
             <Handler type="DiscoveryFeed" Location="/DiscoFeed"/>
         </Sessions>
      </ApplicationOverride>
     </ApplicationDefaults>

So why does the SP think, that the request /acs/Shibboleth.sso/SAML2/POST/ is something that it should ignore?
I also tried to map the path for the status page <Path name="acs/Shibboleth.sso/Status" applicationId="spacs" /> directly: leads to HTTP 404 as well.

/Peter

Am 08.03.2019 um 22:35 schrieb Cantor, Scott:
> On 3/8/19, 4:29 PM, "users on behalf of Aaron Howell" <users-bounces at shibboleth.net on behalf of aaron.howell at deakin.edu.au> wrote:
>
>>  From my reading of the docs - there is a connection between the <ApplicationOverride> handlerURL must be located
>> with in the <RequestMap>’s <Path>
> The handler path(s) must map to the same applicationId as the resources do, that's all.
>
> A 404 is the usual error to get because if the SP doesn't think the request is to something it thinks is a handler for the applicationId that applied to the request, then it will ignore the request, and nothing else is going to respond to it, so you get a normal 404 from there being no path or file with that name.
>
> -- Scott
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20190309/a662874b/attachment.html>