Evolving Attribute Release Policies for campuses
steven_carmody at brown.edu
Tue Apr 5 14:45:10 EDT 2016
Keith Wessel has recently started a couple of interesting threads
related to implementing various portions of a campus Attribute Release
Policy. Recent questions had to do with "Determining optional vs.
required attribute on the consent page?", and "How accurate are the
<md:RequestedAttribute> elements in InCommon and eduGAIN metadata".
I'd like to ask Keith (who is obviously thinking about this space) and
any other campus that is also thinking about deploying User Consent on
Attribute Release to share their current thinking about what their
"complete" policy looks like. User Consent is clearly just a part of the
complete policy -- presumably it only gets triggered for certain SPs ?
How do you combine Consent and R&S ? What is your default release policy
? to IC, to eduGain ? What other special handling is included in your
I think I remember one of the UC campuses talking about their consent
implementation during one of those threads. I'm sure other campuses are
also now trying to develop a policy that covers all the options, and
does so without confusing or overloading users.
So -- Keith (and anyone else) -- what is your current thinking about
your "complete" Attribute Release policy?
More information about the users