You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »


 

Welcome to the Scalable Consent Wiki.

Scalable Consent is an initiative to develop a framework, and working code, in support of effective and informed end-user consent at Internet scale. The intent is to support fine-grained, revocable, informed, and well managed consent services that will allow both user and organization to control the release of their attributes to relying parties throughout an identity ecosystem. The work was catalyzed by an NSTIC grant from NIST, and is being enhanced and maintained by the TIER activity within Internet2. 

The deliverables include:

  •    an architectural model and APIs associated with each flow and component within the model
  •    working code, both as a standalone service and embedded within a Shibboleth IdP, that implements scalable consent across a variety of protocols, including SAML,OIDC, OAuth, etc.
  •    a next-gen UI that allows the user to manage their attribute release in an informed and effective manner
  •    API's and sample connectors that deliver the information for informed consent - services such as RP identification, minimal and optional attributes, information dialogues, histories of prior and similar releases, etc.
  •    enterprise management services to help an organization deploy and management attribute release that integrates both end-user and institutional policies.  
  •    planning documents, discussion materials, and inter-institutional communications to facilitate deployments

The work is intended to help foster an open and interoperable identity ecosystem. Goals include identity portability, improved support for accessibility, and consent that is usable and privacy preserving. All the specifications and code will be open-source.

Scalable Consent Requirements Scalable Consent Requirements.pdf

 

Scalable Consent Overview and Work Plan
Community Resources

Mailing Lists

Information on the EU General Data Protection Regulation (GDPR) - The GDPR has significant impacts on the appropriate use of consent. See the following General Data Protection Regulation (GDPR) and Safer Harbor

Information on Privacy and Consent from the UK ICO. https://ico.org.uk/about-the-ico/privacy-notices-transparency-and-control/

Draft on EU Privacy Code of Conduct - http://www.bbc.com/news/science-environment-35524440 and

Scalable Consent Demo - The PrivacyLens demo site at https://work.iamtestbed.internet2.edu/drupal/ shows the capabilities of PrivacyLens. In addition it illustrates how PL and fine-grain attribute release is a key step towards scalable access control with privacy and security.  In addition to the real-time demo site, there are a set of annotated slides at https://work.iamtestbed.internet2.edu/confluence/display/YCW/Demonstration+Slides.

 

Consent Manager Technical Space

The space, with the design and development work of the Scalable Consent Internals Working Group.

Consent must be consistent across a variety of different protocols. In particular, the user experience should be the same despite differences in the underlying approaches of the two major attribute exchange protocols - SAML and OpenId Connect (OIDC). For a comparison of the two protocols, and the challenges in providing consistent consent, see SAML and OIDC.pdf

PrivacyLens - a next-gen UI

In support of "informed" - plumbing meaningful data and dialogues to users

The previous LARPP site https://wiki.larpp.internet2.edu/confluence/display/LARPP/LARPP+Home



Related Internet2 Middleware projects

 

Work described is supported in part by the National Strategy for Trusted Identities in Cyberspace (NSTIC) National Program Office and the National Institute of Standards and Technology (NIST). The views in this presentation do not necessarily reflect the official policies of the NIST or NSTIC, nor does mention by trade names, commercial practices, or organizations imply endorsement by the U.S. Government.

 

NOTE: All Internet2 Activities are governed by the Internet2 Intellectual Property Framework.

 

  • No labels