Towards a baseline Acceptable Use Policy

Slides:



Advertisements
Similar presentations
EduPerson and Federated K-12 Activities InCommon/Quilts Pilot Group February 27, 2014 Keith Hazelton UW-Madison, InCommon/I2.
Advertisements

INFSO-RI Enabling Grids for E-sciencE JRA3 2 nd EU Review Input David Groep NIKHEF.
SWITCHaai Team Federated Identity Management.
Australian Access Federation Robert Hazeltine Identity and Access Management Enterprise Systems Office.
AARC Overview Licia Florio, David Groep 21 Jan 2015 presented by David Groep, Nikhef.
Authentication and Authorisation for Research and Collaboration Licia Florio AARC Workshop The AARC Project Brussels, 26 October.
JRA1.4 Models for implementing Attribute Providers and Token Translation Services Andrea Biancini.
Authentication and Authorisation for Research and Collaboration David Groep AARC All Hands meeting Milano Policy and Best Practice.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI Evolution of AAI for e- infrastructures Peter Solagna Senior Operations Manager.
JSPG Update David Kelsey MWSG, Zurich 31 Mar 2009.
NMI-EDIT and Rice University Federated Identity Management: Managing Access to Resources in Texas Barry Ribbeck Director System Architecture and Infrastructure.
Networks ∙ Services ∙ People Marina Adomeit FIM4R meeting Virtual Organisation Platform as a Service VOPaaS Nov 30, 2015, Austria Task Leader,
Authentication and Authorisation for Research and Collaboration Peter Solagna, Davide Vaghetti, et al. Topics for PY2 activities.
Authentication and Authorisation for Research and Collaboration Licia Florio AARC CORBEL Workshop The AARC Project Paris, 31 May.
Networks ∙ Services ∙ People Marina Adomeit TNC16 Conference, Prague Towards a platform for supporting collaboration GÉANT VOPaaS
Authentication and Authorisation for Research and Collaboration Peter Solagna, Nicolas EGI AAI integration experiences AARC Project.
Authentication and Authorisation for Research and Collaboration AARC/CORBEL Workshop for Life Sciences AAI AARC Draft Blueprint.
Authentication and Authorisation for Research and Collaboration Taipei - Taiwan Mechanisms of Interfederation 13th March 2016 Alessandra.
Introduction to AAI Services
Boosting AAI for research and collaboration
RCauth.eu CILogon-like service in EGI and the EOSC
Emergency Call Support
Mechanisms of Interfederation
EGI Updates Check-in Matthew Viljoen – EGI Foundation
AAI for a Collaborative Data Infrastructure
AARC Update What’s been happening in AARC which matters for GÉANT
User Community Driven Development in Trust and Identity
eduTEAMS platform for collaboration Niels Van Dijk
eduTEAMS – Current status & Future Plans
Data Virtualization Community Edition
Developing an Online Community for the Sharing of Research
InCommon Steward Program: Community Review
International Energy Agency
The University of North Carolina at Greensboro
AAI Alignment Nicolas Liampotis (based on the work of Mikael Linden)
Project snapshot Adolescents and Agency and Engaging Men and Boys Learning Clusters New Delhi, India October 2017.
Federated Identity Management for Researchers (FIM4R)
Update on FIM4R David Kelsey
Designing a Responsive e-Learning Infrastructure
An AAI solution for collaborations at scale
Boosting AAI for research and collaboration
GÉANT 4-2 JRA3 T1 and T2 Federations and Campus (CaFe) e-Infrastructures and Service Providers (RASP) Daniela Pöhn JRA3 T1 LRZ/DFN-AAI Technology Exchange.
Frameworks for harmonized policies and practices
Policy in harmony: our best practice
EduTEAMS at a Glance Mandeep Saini Linz, Austria 30 May 2017.
Grid Security M. Jouvin / C. Loomis (LAL-Orsay)
OIDC Federation for Infrastructures
Update - Security Policies
AARC Blueprint Architecture and Pilots
Common Authentication and Authorisation Service for Life Science Research Mikael Linden, ELIXIR Finland.
Supporting communities with harmonized policy
EUGridPMA Status and Current Trends and some IGTF topics March 2018 APGridPMA ISGC Meeting David Groep, Nikhef & EUGridPMA.
OIDC Federation for Infrastructures
Chapter 14 Decision Making and Control
AARC2 JRA1 Update Nicolas Liampotis
AAI Architectures – current and future
RCauth.eu CILogon-like service in EGI and the EOSC
WP3: Policy and Best Practice Harmonisation
David Groep for the entire AARC Policy Team I2TechEX18 meeting
EUGridPMA Status and Current Trends and some IGTF topics August 2018 APGridPMA Auckland Meeting David Groep, Nikhef & EUGridPMA.
Community AAI with Check-In
David Groep for the entire AARC Policy Team AARC2 AHM4 meeting
Solving Workplace Problems
Classroom Management Kayla Nakano Education Manager
Baseline Expectations for Trust in Federation
WP6 – EOSC integration J-F. Perrin (ILL) 15th Jan 2019
Federated Incident Response
WISE, SCI & policy templates David Kelsey (STFC-RAL, UK Research and Innovation) FIM4R & TIIME, Vienna, 11 February 2019.
Check-in Identity and Access Management solution that makes it easy to secure access to services and resources.
Team vision and values workshop:
Presentation transcript:

Towards a baseline Acceptable Use Policy Authentication and Authorisation for Research and Collaboration ACAMP input TechEX18, Orlando, FL, USA 2018-10-18

How to prevent users from facing multiple AUPs? No desire to accept a different AUP for each and every service In the simple-proxy model, the proxy can conceivable present a ‘common’ AUP – provided that all back-end SPs agree to a common baseline To make it work for all back-services and e-infrastructures, the basic AUP commandments should be exactly the same for everyone

Difference to commonality in the Baseline AUP – sign once, use everywhere Image: Mozes en de tafelen der Wet, Rembrandt van Rijn, 1659

Scaling Acceptable Use Policy and data release impractical to present user ‘click-through’ screens on each individual service Community conditions Community specific terms & conditions Community specific terms & conditions RI Cluster-specific terms & conditions Common baseline AUP for e-Infrastructures and Research Communities (current draft Baseline AUP – leveraging comparison study and joint e-Infrastructure work) Look ahead to an ACAMP session on a global baseline AUP https://wiki.geant.org/x/P4bWBQ

What about ‘generic enrolment’ AAIs In a composite (‘multi-BPA’) proxy model, that point would naturally shift to the Community AAI logical entrypoint The community known the connected services and proxies, and can present the union of augmented terms alongside the baseline AUP (and the set of Privacy Notices as well) BUT: if users first enroll in the AAI hub, and only then select their community, the community is not yet known and the generic enrolment service is encountered first what should that entry-point present? Can is use the baseline as such? What about ‘connected services’?

The Baseline AUP https://goo.gl/JnUURY

The most controversial word Give us an alternative for ‘Granting Authority’ to stand for community, and/or the agency, or infrastructure name

Christos’ eduTEAMS idea – present AUP for eduTEAMS and hang everything off that org

Or maybe … Make the purpose clause 'for the purpose of participating in activities of research and educational collaborations (“Collaborations"), which are represented in the Service as "Virtual Organizations"‘ and the ‘green paragraph’ in the baseline AUP) to capture the concept of connected services: “The eduTEAMS Service may be used to facilitate access to Connected Services provided by other organizations and/or the GÉANT Association. Access granted by the Service Provider to the eduTEAMS Service does not imply that access to Connected Services is granted. Access to Connected Services available to a Virtual Organization are granted to members of that Virtual Organization by the owner(s) of the Virtual Organization ("Granting Authority"). Users of the Service can be members of more than one Virtual Organizations hosted on the Service. The Baseline clauses of this AUP apply equally to both the eduTEAMS service as well as to all Connected Services, as augmented by any specific terms to which adherence will be required during enrolment in any Virtual Organisation.“ and leave the AUP terms entirely unchanged

And now what ... How can we make it easy for the user, and give enough confidence to the services that they don’t feel the need to show their own AUP and ‘T&C’ unless they are truly unique Can we case the ‘generic enrolment’ case in that common Baseline AUP format?

davidg@Nikhef.nl