Shibboleth2.xml One host element containing two path elements, second path is not routing

[Cantor, Scott]

On 2/27/15, 5:31 PM, "Mark Neidig" <mneidig at ftni.com> wrote:

>Thanks to MikeWho and Scott for their advice. My issue remains 
>unresolved. 

You moved the mistake down one level. You cannot overlap siblings, not 
Hosts, not Paths.

https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPRequestMapHowT
o

>Summary: I am the SP on MS IIS and the scenarios are all IdP initiated. 
>In my shibboleth2.xml file, I have two Path elements within a Host 
>element. The first path always reaches the target. The path listed second 
>gets a Server Error in Application: Method not found message. The same 
>happens when I reverse the order of the paths.

I have no idea what that error means, but the RequestMap is still off, so 
as long as that's the case, it's probably not worth worrying about.

>Question: Given the details below, what do I need to change to get 
>shibboleth to acknowledge the second path?

Stop overlapping siblings.

>Advice step 1 of 2 (Done): (One Host element with two path elements with 
>entity IDs on the path elements, and app IDs as there are different 
>attributes from each IdP)

Different attributes from each IdP is not generally a reason to use 
application overrides.

>Here is an excerpt from my new shibboleth2.xml file:
>
>	<Host name="test.remitpro.com" scheme="https" port="443" >
>		<Path name="/SignIn/path1"  applicationId="path1" requireSession="true" 
>authType="shibboleth"/>
>		<Path name="/SignIn/path2"   applicationId="path2"     
>requireSession="true" authType="shibboleth"/>
>	</Host>

Those Paths overlap. You can't do that, and the native log will warn you 
when it sees that.

<Path name="SignIn">
	<Path name="path1"/>
	<Path name="path2"/>
</Path>

-- Scott