v3 consent to attribute release : half-thoughts on UIs

[Jim Fox]

For us the attributes will have to be displayed in some text understandable by our users.

Jim

On Wed, 17 Sep 2014, Marvin Addison wrote:

> Date: Wed, 17 Sep 2014 11:59:55
> From: Marvin Addison <marvin.addison at gmail.com>
> To: Shib Dev <dev at shibboleth.net>
> Reply-To: Shib Dev <dev at shibboleth.net>
> Subject: Re: v3 consent to attribute release : half-thoughts on UIs
> 
>> The management page ... would display one or more relying parties and the attributes
>> (and values) that have either been approved or declined by the user
>> for release.
>
> Virginia Tech is very much interested in the management page. Here's a
> minimal version of what we imagined:
>
> https://www.middleware.vt.edu/pubs/shib/uapprove-mock/prefs.html
>
>> Besides a reset button, the user could be able to toggle
>> approve|deny at the granularity of relying party, attribute, or
>> attribute value.
>
> I thought that the notion of per-attribute release control was ruled
> out in a recent discussion. Maybe I'm remembering wrong.
>
> M
> -- 
> To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
>