Metadata question for Embedded Discovery and SP authentication of IdP

[Chad La Joie]

Scott will correct me if I'm wrong, but pretty much all our software
will just use the first value of any multi-valued thing in metadata.

On Wed, Aug 3, 2011 at 08:40, Tom Scavo <trscavo at gmail.com> wrote:
> On Tue, Aug 2, 2011 at 6:48 PM, Jason Bau <jasonbau at gmail.com> wrote:
>>
>> The Stanford Metadata is here:
>>
>> https://idp.stanford.edu/metadata.xml
>
> AFAICT, the above metadata is functionally equivalent to the metadata
> in the InCommon aggregate except that the latter contains an extra
> SingleSignOnService endpoint. Normally, that wouldn't be a problem,
> but that endpoint is a duplicate of an existing endpoint:
>
> <SingleSignOnService
>    Binding="urn:mace:shibboleth:1.0:profiles:AuthnRequest"
>    Location="https://idp.stanford.edu/shibboleth-idp/SSO"/>
> <SingleSignOnService
>    Binding="urn:mace:shibboleth:1.0:profiles:AuthnRequest"
>    Location="https://idp.stanford.edu/idp/profile/Shibboleth/SSO"/>
>
> This is a question for Scott: What does the software do when it
> encounters two non-indexed endpoints with identical Binding
> attributes?
>
> Tom
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered