Intro and Agenda Setting Room: 31/S-028

Establishing the requirements for the future Room: 31/S-028 What are the requirements for a WLCG AuthZ system? https://docs.google.com/document/d/1hnsPWf9C7ODVXZ7JehsSEiEsQwf5UmqLfTwVDhuqHzk/edit#heading=h.xam6oit8esxs

Summary of the agreed requirements Room: 31/S-028

Review of existing or potential solutions and strategies Room: 31/S-028 Aim is to come up with a strategy for how to address our requirements. Split into roughly two sections, "Front end" i.e. impacting users, and "Back end" i.e. what's going on under the hood. ----Front end---- Authentication mechanisms - X.509 - SAML - OpenID Connect - Social logins Identity/Collaboration management/Authorization services - VOMS Admin - INDIGO IAM - EGI Check-in - CoManage - Keycloak - Argus ----Back end---- Authorization - VOMS attribute certificate - OAuth bearer token - JWTs - Other token format (Macaroons) - SAML assertion Token Translation - Master Portal - WATTS

Consensus, conclusions and next steps Room: 31/S-028