Abstract
Since 2017, the Worldwide LHC Computing Grid (WLCG) has been working towards enabling token based authentication and authorisation throughout its entire middleware stack. Following the publication of the WLCG Common JSON Web Token (JWT) Schema v1.0 [1] in 2019, middleware developers have been able to enhance their services to consume and validate the JWT-based [2] OAuth2.0 [3] tokens and process the authorization information they convey. Complex scenarios, involving multiple delegation steps and command line flows, are a key challenge to be addressed in order for the system to be fully operational. This paper expands on the anticipated token based workflows, with a particular focus on local storage of tokens and their discovery by services. The authors include a walk-through of this token flow in the RUCIO managed data-transfer scenario, including delegation to FTS and authorised access to storage elements. Next steps are presented, including the current target of submitting production jobs authorised by Tokens within 2021.
Highlights
Over the past few years there has been significant progress made towards making token based authentication and authorisation a realistic goal for the Worldwide LHC Computing Grid (WLCG)
The Data Organization, Management and Access (DOMA) Third-Party-Copy (TPC) Working Group [11] has been instrumental in getting WLCG token support tested in data handling workflows that will be vital for LHC Run 3 and beyond
The WLCG Common JSON Web Token (JWT) Schema v1.0 was published in September 2019 [1] and defined the semantics for JWT use within the WLCG
Summary
The current objective is to be able to submit experiment production jobs within 2021
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
