<div dir="ltr"><div>In reading the documentation, it seems to allow the use of multiple session initiators, you need to put them inside a "Chaining" SessionInitiator definition.<br></div><div><br></div>I guess that part of my confusion is that only place I've seen "Location" set is in the chaining session initiator definition, e.g.<div>
<br></div><div><div> <SessionInitiator type="Chaining" Location="/DS" id="DS" isDefault="true" relayState="cookie" acsByIndex="false"></div><div><br></div>
<div>or</div><div><br></div><div> <SessionInitiator type="Chaining" Location="/Login" isDefault="true" id="Login" entityID="<a href="https://shibboleth.example.edu/idp/shibboleth">https://shibboleth.example.edu/idp/shibboleth</a>"></div>
</div><div><br></div><div>I might guess that the first one is actually a SAMLDS initiator, and that the second is a SAML2 initiator, but if I add location "/DS" to the SAMLDS definition contained in the Chaining definition, the "/DS" location isn't available. My goal is to enable both the /DS and /Login locations, but I think that Scott's previous message suggests that that might not (probably isn't) necessary?</div>
<div><br></div><div>Liam</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Feb 17, 2014 at 11:32 AM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 2/17/14, 11:27 AM, "Liam Hoekenga" <<a href="mailto:liamr@umich.edu">liamr@umich.edu</a>> wrote:<br>
><br>
>Is it possible to enable both the DS and Login endpoints at the same<br>
>time? The only configuration I see that mentions either location is<br>
>the top level of the "Chaining" session initiator definition.<br>
<br>
</div>Neither has any meaning to the software, there are session initiator<br>
endpoints and that's it. What they do is up to the configuration.<br>
<br>
The <SSO> element defaults to a single initiator at /Login. Defining more<br>
than one requires adding SessionInitiators manually.<br>
<br>
Whether you need to depends on the use case. Defining a discoveryURL and<br>
no entityID in the <SSO> element will default to requesting discovery. You<br>
can then override that with entityID content settings for specific<br>
locations and possibly avoid anything extra.<br>
<br>
-- Scott<br>
<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</blockquote></div><br></div>