Page MenuHomePhabricator

Decouple Toolforge API gateway authentication from Kubernetes certificates
Open, HighPublic

Description

The Toolforge API gateway is responsible for authenticating and routing API requests to control Toolforge tools. Right now the authentication part is implemented via client certificates signed by the Kubernetes cluster client CA. This works okay for now, but blocks implementing some new features or improvements. For that reason we need to implement a new authentication system for various API clients to use.

Proposal

There is a draft here: https://wikitech.wikimedia.org/wiki/User:Taavi/EnhancementProposals/Toolforge_API_authentication_decoupling_MVP

Event Timeline

Somehow I missed this, we re-took this discussion here T363983: [toolforge] Investigate authentication, leaning on using idp/CAS instead of oauth, at least for starters (same auth as horizon)

@taavi should I close this as duplicate? Or do you want to refresh/extend the oauth+dedicated auth server specific proposal?

dcaro triaged this task as High priority.Apr 16 2025, 2:22 PM

@taavi should I close this as duplicate? Or do you want to refresh/extend the oauth+dedicated auth server specific proposal?

I'm planning to come up with a refreshed proposal here.