v3 consent to attribute release : ask-again ?

[Lukas Hämmerle]

> Mostly I've been looking at the picture on the uApprove page [1].
> 
> [1] https://www.switch.ch/aai/support/tools/uApprove.html

I just updated that picture because so far it has not included the MDUI
element Privacy Statement URL and Information URL.


On 21.08.14 01:29, Cantor, Scott wrote:
> But I'm inclined to believe that fewer choices is best

Yes, that's the current approach for uApprove which has worked quite
well so far for our users in SWITCHaai because it seems a pragmatic
trade-off between usability and informed consent.

It's a simple all-or-nothing choice basically with the (configurable)
option to completely skip uApprove per user (=global consent).


> and that the "if
> anything changes" part should just be a deployment choice

That's the default in uApprove currently. If an attribute value changes
or if additional attributes are released to an SP, uApprove asks for
consent again.

However, once given, the consent is valid for ever for that particular
SP (unless the values change or additional attributes are released).


Best Regards
Lukas


-- 
SWITCH
Lukas Hämmerle, Central Solutions
GÉANT Project Task Leader "Enabling Users"
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland
phone +41 44 268 15 05, direct +41 44 268 15 64
lukas.haemmerle at switch.ch, http://www.switch.ch