WLCG AuthZ Call
Previous Actions:
- Tom: Provide GoogleDrive link for CHEP submission - done, see below
- Jim: Update PR paragraph based on discussion and circulate once done. - PR updated, awaiting final reviewers: https://github.com/WLCG-AuthZ-WG/common-jwt-profile/pull/19
- Paul: Produce a PR following the "Tokens with groups and explicit AuthZ statements" email thread
Proposed agenda:
- Review Previous Actions
- ATLAS IAM Incident Postmortem
- CHEP Submission - final calls
- WLCG workshop recap (if participants present)
Zoom meeting:
Link below, in the videoconference section. Please ensure you are signed in to Indico to see the meeting password!
Next Meeting:
- 25th November
Present: Liz, Maarten, Hannah, Petr, Brian, Federica, Max, John, Dimitrios, Jim, Francesco, Thomas, Roberta, Marcelo, Martin, Andrei, Douglas, DaveD, Mine, Tommaso, Xin
Apologies: Tom Dack
Minutes:
ATLAS IAM Postmortem discussion - please see PDF
Notes:
- During postmortem, WLCG Crisis procedure not followed. Added to postmortem doc.
- How to avoid DDOS?
- Keep stats of normal use and trigger warnings if that changes
- Add a delay after token request (CILogon has 4 requests per second per IP)
- Do we need to keep access tokens in IAM DB?
- Theoretically not if we accept that they are not revocable
- Even the introspection endpoint could be coded in a way that avoids a DB lookup
- General feeling is that we should not revoke them but the timeline of tokens might need to be extended
- Followups
- Investigate rate limiting with NGINX for WLCG IAM deployments
Topic note from mail thread from Brian:
> Seems that if IAM's going to insert issued tokens into a database then it requires built-in circuit breakers to protect itself from a runaway client. (Personally, I think it illustrates the problem of using a database as a logging system ... there's no use case beyond SEIM for these particular tokens).
CHEP Abstract
WLCG Workshop
Summary of Actions: