Please Comment on the Charter Below
Please leave your comments below on whether you feel this approach encouraging campuses to establish default attribute release policies, will further federated access to collaborative and academic resources.
DRAFT Charter
The Attributes for Collaboration and Federation Working Group will:
Recommend a default Attribute Release Policy (ARP) for InCommon participants
R&S for R&S SPs
Recommended ARP for all other SPs - in addition to, or a subset of, R&S
Develop (and Execute*) a Roadmap for Adoption of Attribute Release Policies (using the draft Steering Roadmap as a starting point)
Outreach [Steering] - Identify the needed stakeholder groups, and identify or create the content and use cases that can educate those groups.
Survey [Working Group] - Possible survey of the community on why attributes are NOT being released - identify obstacles (maybe webinar?) - completed by campus stakeholders as well as IAM person.
Consent [Working Group] - Determine where “Consent” fits into the roadmap
Communication [ALL] - Create a communication plan to inform InCommon Participants of recommendations and steps being taken to enable basic federated access
Review and enhance online content for IdP admins so they have a clear set of steps to follow to implement the desired approach (including possibly consent) once campus policy decisions have been approved.
Discuss making some level of attribute release (e.g. R&S) part of a future version of the AAC’s Baseline Expectations for IdPs.
*Out-of scope for this Working Group is:
[Phase 2 unless pulled into Current WG Tasks] - Consider collaborating with TIER software packaging and InCommon Ops to give stakeholders some control via a set of tools (e.g. local - similar to consent; new IC services (eg suggested Attribute Release Policies); etc)) to simplify and automate attribute release management.
Depending on time required to complete above items, “Execution” of the Roadmap may be a Phase 2 effort (after Tech Exchange).