OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

security-services-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [security-services-comment] SAML V2.0 Metadata Extensions forLogin and Discovery

On Thu, Jan 20, 2011 at 8:42 PM, Cantor, Scott E. <cantor.2@osu.edu> wrote:
>> It seems the <mdui:UIInfo> element is applicable at the level of the
>> <AttributeConsumingService> element but there doesn't seem to be a
>> mechanism to do that. Related to this, it seems the precedence
>> described in section 2.3.3 is wrong. Shouldn't the ServiceName and the
>> ServiceDescription in the <AttributeConsumingService> element take
>> precedence over the <mdui:UIInfo> child elements?
> Creating that precedence just amounts to omitting the extension, so there's no need to define such an ordering. If the extension is present, then it's meant to take over.

Yes, I see that now. If an SP defines one or more
<AttributeConsumingService> elements, it should probably just omit
<mdui:DisplayName> and <mdui:Description>. Still, there's no way to
apply the other elements (logos, e.g.) at the level of the service.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]