© 2006 Open Grid Forum Interpreting bags of VOMS ACs Extending GFD.182 in Authorization Scenarios Supported by the Initiative for Globus in Europe, IGE.

Slides:



Advertisements
Similar presentations
© 2006 Open Grid Forum GHPN-RG Status update co-chairss:Cees de Laat Dimitra Simeonidou GGF22, Boston, February 2008.
Advertisements

© 2006 Open Grid Forum JSDL 1.0: Parameter Sweeps OGF 23, June 2008, Barcelona, Spain.
© 2006 Open Grid Forum Network Services Interface OGF30: Connection Services Guy Roberts, 27 th Oct 2010.
© 2006 Open Grid Forum Network Services Interface Introduction to NSI Guy Roberts.
© 2006 Open Grid Forum JSDL 1.0: Parameter Sweeps: Examples OGF 22, February 2008, Cambridge, MA.
© 2006 Open Grid Forum OGF19 Federated Identity Rule-based data management Wed 11:00 AM Mountain Laurel Thurs 11:00 AM Bellflower.
© 2007 Open Grid Forum JSDL-WG Session OGF27 – General Session 10:30-12:00, 14 October 2009 Banff, Canada.
©2010Open Grid Forum OGF28 OGSA-DMI Status Chairs: Mario Antonioletti, EPCC Stephen Crouch, Southampton Shahbaz Memon, FZJ Ravi Madduri, UoC.
© 2006 Open Grid Forum Joint Session on Information Modeling for Computing Resources OGF 20 - Manchester, 7 May 2007.
© 2007 Open Grid Forum JSDL-WG Session OGF21 – Activity schema session 17 October 2007 Seattle, U.S.
© 2006 Open Grid Forum 2 nd March 09 Enterprise Grid Requirements Research Group OGF25 EGR-RG Session Group.
© 2008 Open Grid Forum Resource Selection Services OGF22 – Boston, Feb
© 2006 Open Grid Forum Network Services Interface OGF29: Working Group Meeting Guy Roberts, 19 th Jun 2010.
© 2007 Open Grid Forum JSDL-WG Session 1 OGF25 – General Session 11:00-12:30, 3 March 2009 Catania.
© 2006 Open Grid Forum JSDL Optional Elements OGF 24 Singapore.
© 2007 Open Grid Forum Data/Compute Affinity Focus on Data Caching.
© 2007 Open Grid Forum OGSA-RUS Specification Update, Adoption and WS-RF Profile Discussions (Molly Pitcher) Morris Riedel (Forschungszentrum Jülich –
© 2006 Open Grid Forum Joint Session on Information Modeling for Computing Resources (OGSA Modeling Activities) OGF 21 - Seattle, 16 October 2007.
© 2006, 2007 Open Grid Forum Michel Drescher, FujitsuOGF-20, Manchester, UK Andreas Savva, FujitsuOGF-21, Seattle, US (update) Extending JSDL 1.0 with.
© 2009 Open Grid Forum Usage Record Working Group Alignment and Production Profile.
1 ©2013 Open Grid Forum OGF Working Group Sessions Security Area – FEDSEC Jens Jensen, OGF Security Area.
OGF26 Grid Information Retrieval Research Group May 26, 2008 Chapel Hill.
© 2006 Open Grid Forum DCI Federation Protocol BoF Alexander Papaspyrou, TU Dortmund University Open Grid Forum March 15-18, 2010, Munich, Germany.
© 2007 Open Grid Forum Data Grid Management Systems: Standard API - community development Arun Jagatheesan, San Diego Supercomputer Center & iRODS.org.
© 2006 Open Grid Forum Service Level Terms Andrew Grimshaw.
© 2010 Open Grid Forum Standards All Hands Meeting OGF28, München, March 2010.
© 2006 Open Grid Forum Network Services Interface OGF 32, Salt Lake City Guy Roberts, Inder Monga, Tomohiro Kudoh 16 th July 2011.
© 2007 Open Grid Forum Enterprise Best (Community) Practices Workshop OGF 22 - Cambridge Nick Werstiuk February 25, 2007.
© 2010 Open Grid Forum OCCI Status Update Alexander Papaspyrou, Andy Edmonds, Thijs Metsch OGF31.
© 2007 Open Grid Forum JSDL-WG Session OGF22 – General Session (11:15-12:45) 25 February 2008 Boston, U.S.
© 2006 Open Grid Forum BES 1.1 Andrew Grimshaw. © 2006 Open Grid Forum 2 OGF IPR Policies Apply “ I acknowledge that participation in this meeting is.
© 2006 Open Grid Forum FEDSEC-CG Andrew Grimshaw and Jens Jensen.
© 2006 Open Grid Forum Activity Instance Schema Philipp Wieder (with the help of the JSDL-WG) Activity Instance Document Schema BoF Monday, 25 February,
© 2006 Open Grid Forum Network Services Interface OGF 33, Lyon Guy Roberts, Inder Monga, Tomohiro Kudoh 19 th Sept 2011.
© 2015 Open Grid Forum ETSI CSC activities Wolfgang Ziegler Area Director Applications, OGF Fraunhofer Institute SCAI Open Grid Forum 44, May 21-22, 2015.
© 2006 Open Grid Forum HPC Job Delegation Best Practices Grid Scheduling Architecture Research Group (GSA-RG) May 26, 2009, Chapel Hill, NC, US.
© 2006 Open Grid Forum GridRPC Working Group 15 th Meeting GGF22, Cambridge, MA, USA, Feb
OGSA-RSS Face-to-Face Meeting Sunnyvale, CA, US Aug 15-16, 2005.
© 2008 Open Grid Forum OGSA-DMI WSDL Renderings & Interop OGF23 OGSA-DMI session Michel Drescher 2 June, 2008 Barcelo Sants Hotel.
© 2006 Open Grid Forum Network Services Interface CS Errata Guy Roberts, Chin Guok, Tomohiro Kudoh 29 Sept 2015.
© 2006 Open Grid Forum OGSA-WG: EGA Reference Model GGF18 Sept. 12, 4-5:30pm, #159A-B.
© 2006 Open Grid Forum Remote Instrumentation Services in Grid Environment Introduction Marcin Płóciennik Banff, OGF 27 Marcin Płóciennik.
© 2006 Open Grid Forum Grid High-Performance Networking Research Group (GHPN-RG) Dimitra Simeonidou
© 2006 Open Grid Forum NML Progres OGF 28, München.
© 2008 Open Grid Forum PGI - Information Security in the UNICORE Grid Middleware Morris Riedel (FZJ – Jülich Supercomputing Centre & DEISA) PGI Co-Chair.
© 2007 Open Grid Forum OGF Management Area Meeting OGF20 7 May, am-12:30pm Manchester, UK.
© 2007 Open Grid Forum Status Reviews and Plans Production Grid Infrastructure (PGI) - WG Morris Riedel et al. Juelich Supercomputing Centre PGI Co-Chair.
© 2006 Open Grid Forum VOMSPROC WG OGF36, Chicago, IL, US.
© 2007 Open Grid Forum OGF20 Levels of the Grid Workflow Interoperability OGSA-WG F2F meeting Adrian Toth University of Miskolc NIIF 11 th May, 2007.
© 2006 Open Grid Forum Network Services Interface 2015 Global LambdaGrid Workshop Prague Guy Roberts, Chin Guok, Tomohiro Kudoh 28 Sept to 1 Oct 2015.
© 2008 Open Grid Forum Production Grid Infrastructure WG State Model Discussions PGI Team.
© 2007 Open Grid Forum JSDL-WG Session OGF26 – General Session 11:00-12:30, 28 May 2009 Chapel Hill, NC.
Network Services Interface
Welcome and Introduction
RISGE-RG use case template
GridRPC Working Group 13th Meeting
Grid Resource Allocation Agreement Protocol
OGF session PMA, Florence, 31 Jan 2017.
Sharing Topology Information
Network Services Interface
Network Services Interface Working Group
OGSA-Workflow OGSA-WG.
Network Measurements Working Group
WS Naming OGF 19 - Friday Center, NC.
Activity Delegation Kick Off
Network Services Interface Working Group
OGSA-RSS-WG EPS Discussion.
Introduction to OGF Standards
Proposed JSDL Extension: Parameter Sweeps
OGF 40 Grand BES/JSDL Andrew Grimshaw Genesis II/XSEDE
Presentation transcript:

© 2006 Open Grid Forum Interpreting bags of VOMS ACs Extending GFD.182 in Authorization Scenarios Supported by the Initiative for Globus in Europe, IGE IGE (RI ) is funded by the European Commission under Framework Programme 7

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI OGF IPR Policies Apply “ I acknowledge that participation in this meeting is subject to the OGF Intellectual Property Policy. ” Intellectual Property Notices Note Well: All statements related to the activities of the OGF and addressed to the OGF are subject to all provisions of Appendix B of GFD-C.1, which grants to the OGF and its participants certain licenses and rights in such statements. Such statements include verbal statements in OGF meetings, as well as written and electronic communications made at any time or place, which are addressed to: the OGF plenary session, any OGF working group or portion thereof, the OGF Board of Directors, the GFSG, or any member thereof on behalf of the OGF, the ADCOM, or any member thereof on behalf of the ADCOM, any OGF mailing list, including any group list, or any other list functioning under OGF auspices, the OGF Editor or the document authoring and review process Statements made outside of a OGF meeting, mailing list or other function, that are clearly not intended to be input to an OGF activity, group or function, are not subject to these provisions. Excerpt from Appendix B of GFD-C.1: ” Where the OGF knows of rights, or claimed rights, the OGF secretariat shall attempt to obtain from the claimant of such rights, a written assurance that upon approval by the GFSG of the relevant OGF document(s), any party will be able to obtain the right to implement, use and distribute the technology or works when implementing, using or distributing technology based upon the specific specification(s) under openly specified, reasonable, non- discriminatory terms. The working group or research group proposing the use of the technology with respect to which the proprietary rights are claimed may assist the OGF secretariat in this effort. The results of this procedure shall not affect advancement of document, except that the GFSG may defer approval where a delay may facilitate the obtaining of such assurances. The results will, however, be recorded by the OGF Secretariat, and made available. The GFSG may also direct that a summary of the results be included in any GFD published containing the specification. ” OGF Intellectual Property Policies are adapted from the IETF Intellectual Property Policies that support the Internet Standards Process.

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI Background in five points VOMS attributes are the most common mechanism to convey community membership in particular as ACs in proxy chains have well defined syntax format and conveyance mechanism: GFD.182 are used as basis for authZ decisions but the ‘valid result attribute set’ is only crudely defined and potentially ‘leaky’

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI Current parsing rules (GFD.182) 4.4Proxy certificate chain handling During normal job execution in a grid environment, a proxy may be delegated several times, and each delegated proxy may obtain a new set of AC. This subsection will detail how these ACs MUST be evaluated. Let us call the user certificate cert0. The proxy generated from it is cert1, the proxy generated from cert1 is cert2, and so on until the latest delegation, called certN. During the evaluation procedure, the chain is parsed in order from certN to cert0. When an AC is found in certI, all subsequent ACs in certJ with J<I MUST be ignored. In other words, only the most recent attribute certificate must be evaluated. 4

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI To whom does the AC apply? The VOMS ACs are bound to the EEC of the holder as per “Note that the holder here is the user’s own PKC, and NOT the proxies he may use.” Based on issuer and serial, and may carry any attribute currently asserted for the holder Not linked to the proxy (which is good), so can be rebound to the end of any proxy chain, and will ‘upgrade’ any such chain (bad?) 5

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI Chain downscoping Currently, anyone who can obtain a proxy chain and leaf PK can ‘explode’ scope to any VO and any FQANs held by the subject significantly increases exposure, also for ‘inadvertent’ renewals where scoping is used to protect your own resources we need to allow for renewal – so time extension should be exempt from scoping Proposal set of valid attributes - from any VO - can only be equal or less wide than the valid set of the next- higher-level proxy 6

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI Open Issues Is the ‘multiple VO’ feature actually used? If so, the ordering must be defined and ordering must be predictable in proxy production tools Do we agree revocation is out of scope? Do we want to add ‘downscoping’ to the validation rules? For both FQANs and generic attributes For all included VOs But not for time constraints (to allow renewal)? 7

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI Time line and plans Prerequisites: input from VOMS team input from main validation service providers, including EMI’s CAL and in LCMAPS ‘verify-proxy’ for use via gt4-authz- callout for IGE Does not impact authZ services proper Target a good draft by OGF35 (Delft) in June which WG to adopt this work? Or a new group? 8

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI Scope The recommended interpretation for ACs in chained identity credentials: determining the effective attribute set for collated VOMS attributes the order in which attributes are interpreted what to do if one out of a bag of VOMS ACs at the same level is expired 9

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI Revision/extension of GFD.182 Review the use cases for non-criticality of the VOMS extension (document in update) “Accessing a resource, where the user requires the resource to treat the user as a having a specific attribute (set)” Replace section

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI New group targets Spin up a new group “VOMS Attribute Processing (VOMSPROC)” 1 st doc (REC): canonicalization of VOMS ACs in chained identity credentials timeline: OGF35 2 nd doc (INFO): understanding parsing rules for collated VOMS SAML space timeline OGF36+ Target audience to include also GridSite, EMI CAL, C, gLiteTM, PERMIS, Globus, and the VOMS PT. 11

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI A new (quick) group? Then we would need to answer the canonical 7 questions … 1.Is the scope of the proposed group sufficiently focused? 2.Are the topics that the group plans to address clear & relevant 3.Will the formation of the group foster (consensus–based) work that would not be done otherwise? 4.Do the group’s activities overlap inappropriately with those of another OGF group? 5.Are there sufficient interest and expertise in the group’s topic? 6.Does a base of interested consumers appear to exist for the planned work? 7.Does the OGF have a reasonable role to play? 12

© 2006 Open Grid Forum Supported by IGE, the Initiative for Globus in Europe which is co-funded by the European Commission under contract RI Full Copyright Notice Copyright (C) Open Grid Forum (2012). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors or assignees.