Skip to Content.
Sympa Menu

shibboleth-dev - Re: [Shib-Dev] [IdPv3] Consent Engine Work

Subject: Shibboleth Developers

List archive

Re: [Shib-Dev] [IdPv3] Consent Engine Work


Chronological Thread 
  • From: Tom Scavo <>
  • To:
  • Subject: Re: [Shib-Dev] [IdPv3] Consent Engine Work
  • Date: Fri, 24 Sep 2010 10:34:08 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=aI5Zn8RmFOaDdKgMQdHk8my5/HzWClTg6kJJ8e+C185bMcs8bW7idIIRc9RurepnX+ Hp/HKdbtB43X1q6QjrI4wgOJwTD6lsOREI7dVs4fQxQ8F2NcHGHVpsjnX3ney3bZgcUW Q2lFEd21XkdDm8jw97dNijRcUoCQlRAx19gAA=
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

Archive powered by MHonArc 2.6.16.

Top of Page