Evolving Attribute Release Policies for campuses

Cantor, Scott cantor.2 at osu.edu
Tue Apr 5 19:16:56 EDT 2016

On 4/5/16, 6:56 PM, "users on behalf of Scott Koranda" <users-bounces at shibboleth.net on behalf of skoranda at gmail.com> wrote:

>I do not see that IdPv3 consent, when configured in a
>way that examines the SP metadata for requested attributes
>and their required/optional flag, helps with attribute
>release and interoperability in the eduGAIN context.

Just a point of clarification...I may be misremembering something, but at present I don't think there is any connection between the metadata's list of attributes requested and the consent feature. The UIInfo extension is used, but I think that's it.

I'm aware there are people who want a connection made, just saying it's not there at the moment.

As I said on the MACE-Dir call yesterday, I believe that the basis of the R&S work was very much to avoid selective release of any attributes in the bundle, and I don't think it's a good idea to combine those concepts.

-- Scott

More information about the users mailing list