Shibboleth Developers

[Tom Scavo <>]

On Fri, Sep 24, 2010 at 10:38 AM, Chad La Joie 
<>
 wrote:
> That's an implementation detail that is not know yet since the code hasn't
> really been started.  It's safe to say that the metadata UI extension draft
> that Scott just submitted to OASIS will be looked at.

Section 2.3.3 of that document recommends an ordering that includes
<md:ServiceName>, so presumably it would come into play. In fact,
since <md:ServiceName> is a required child element of
<md:AttributeConsumingService>, it is likely that both
<mdui:DisplayName> and <md:ServiceName> will be available in metadata.
If the latter were profiled as a more fine-grained name, maybe both
could be displayed, I don't know.

In any event, InCommon metadata will most likely contain
<md:AttributeConsumingService> elements in the near future (no
timeline yet). So the more interesting question is: will the consent
engine consume <md:RequestedAttribute> elements?

Tom

> On 9/24/10 11:34 AM, Tom Scavo wrote:
>>
>> On Wed, Jun 9, 2010 at 9:48 AM, Chad La 
>> Joie<>
>>   wrote:
>>>
>>> - A page the displays the attributes to be released along with the
>>> service
>>> provider name/description.  Attribute name and description will be
>>> configured in the attribute resolver config, SP name and description will
>>> come from metadata.  All names and descriptions supports
>>> internationalization.
>>
>> Will the SP name and description come from
>> md:AttributeConsumingService/md:ServiceName and
>> md:AttributeConsumingService/md:ServiceDescription elements,
>> respectively? Assuming that's the case, will the included
>> md:RequestedAttribute elements be consumed by the consent engine?
>>
>> Tom
>>
>
> --
> Chad La Joie
> http://itumi.biz
> trusted identities, delivered
>