This would involve making it easier for external users to use their own providers for user login such as github or something other than auth0. This does not block initial redeployment because mozilla internal clusters can just use our auth0 stuff.

Eli, can you update this with the current state of what we think we need to do with this?

Breaking this out into time periods for which the requirements will change: Immediate term: No action necessary. If the goal for the initial redeployment is to replicate our current environment, then nothing needs to be done as we can continue to use manual login and our current Auth0 production client, provided that the deployment also exists at the current domains and subdomains. Medium term: Support GitHub logins. The UI will need a generic way to interact with a login provider and get a profile which can be exchanged for Taskcluster credentials. Right now we support Auth0 via OIDC in the login service, but that won't work for GitHub. Long term: Support pluggable login providers. It should be possible for cluster admins to choose a login plugin, or write a login plugin, that has an API contract that either the login service or the UI backend can understand, which would then provide a generic way for the UI to get a user profile.

Note: if the initial deployment is not our current production environment, but still an Auth0 environment, there should still be nothing necessary from a UI perspective.

As Eli has said, nothing to do here at the moment, but I expect it will soon be time to start designing something soon, especially when we have a clearer picture of what a redeployed tools UI looks like. I don't think I'm the right person to lead that charge -- given that I've been involved in login v2 through login v7, my track record isn't great :) Eli, can you lead the charge here?

Sure thing. I'll make a point to have an informal discussion about this at the SF 2018 All Hands.

https://github.com/taskcluster/taskcluster-web-server/pull/14 https://github.com/taskcluster/taskcluster-web/pull/88

This is not necessarily part of r13y, but part of the tc-web project.