Shibboleth Developer's Meeting, August 22, 2014
Call Administrivia
10:00 Central US / 11:00 Eastern US / 16:00 UK
Normal schedule is to skip next Friday as it's the last Friday of the month. Any reason to vary that?
60 to 90 minute call window.
This week's call will use the Lync system at OSU on an experimental basis. To participate, call:
- +1 (614) 688-1800 (please use if possible)
- +1 (800) 678-6114 (use only if you're charged for the 614 number)
The Conference ID is: 738127#
International participants should be able to access the 800 number without charge through Skype.
Fallback Call Details
If the above doesn't work out, we will fall back to the previous system at 15 minutes past the hour.
Attendees:
Brent
...
However, I was confused as to what "rejecting" consent would mean on a per-attribute basis, what the timeline would be for asking for consent again, etc, so I posted a quick note to the dev list, and that led me to the PrivacyLens and GakuNin forks. I also did some quick internet searches for "user attribute consent" and realized that quite a bit of work has been done already, the document that made me feel the "best" was this one, which says that IdPv3 will NOT include a per-attribute consent GUI. For other projects with consent UIs, see SimpleSAMPphp and Cirrus Identity et al. I liked this page because it displays a matrix for required vs optional attributes and a UI, for which I wonder how it would look on a small screen. I was also pretty clueless until now, and still really am, regarding REFEDS Attribute Release Recommendations. ..
After a whirlwind tour through attribute release consent, I am left pretty much where I started, that I should port uApprove v2 to v3, leaving room for per-attribute consent, but defer UI work until later.
Other