Closed Bug 1395358 Opened 7 years ago Closed 7 years ago

Use auth0 for tools login, and get TC credentials from there

Categories

(Taskcluster :: Services, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

References

Details

This is the culmination of work to stop using Okta. The idea is to use https://docs.taskcluster.net/reference/integrations/taskcluster-login/docs/getting-user-creds instead of the current collaboration with login. Okta, and with it the current federated login support, is going away in October, so there's a time limit here.
Assignee: nobody → dustin
Blocks: 1380028
Step 1: use taskcluster-client-web Step 2: auth with Auth0 SPA Step 3: clean up credentials manager
Note to self: setting up a client with callback https://taskcluster-tools.ngrok.io/oidc-login
..in REQ0051246
Commit pushed to master at https://github.com/taskcluster/taskcluster-tools https://github.com/taskcluster/taskcluster-tools/commit/8f7570f7470f459acd362ab06e5506c21e80ece6 Bug 1395358 (part 1) - use taskcluster-client-web (#298) * Bug 1395358 - use taskcluster-client-web instead of taskcluster-client * Bug 1395358 - use .use for authorizedScopes in actions
ClientId requested in REQ0051591.
Commits pushed to master at https://github.com/taskcluster/taskcluster-tools https://github.com/taskcluster/taskcluster-tools/commit/21299723ce7d6685fda73f194a853d726db1fe4d Bug 1395358 - add auth0 login support https://github.com/taskcluster/taskcluster-tools/commit/8187b709f3a5b0aba9d03e1b2af1cec9c37d989a Bug 1395358 - switch to UserSession for tracking user session Use a UserSession instance nstead of "credentials", since we don't always have credentials and need to be a little smarter about the current user. The "Clients" component is updated to take a UserSession and hand the appropriate information to the client constructors. The Credentials Manager is updated to load the credentials asynchronously and to display the username and, for debugging purposes, user ID. The client editor is updated to wait for credentials to load before displaying, so that it can use the clientId to guess at clientIds it should display/create. https://github.com/taskcluster/taskcluster-tools/commit/f37457de32d1e494bf2756c4d9721db36551310e Bug 1395358 - fix error handling in indexed artifact browser https://github.com/taskcluster/taskcluster-tools/commit/32a0cf323878dbd808d6d76bc0988556850c0acf Bug 1395358 - show user picture when logged in https://github.com/taskcluster/taskcluster-tools/commit/8f53f47e879a80b5d264de938f9c9a1fdb545edf Bug 1395358 - refactor auth stuff into AuthController This drastically simplifies the CredentialsMenu, Naviagation, and App, centralizing the auth-related concerns in src/auth. https://github.com/taskcluster/taskcluster-tools/commit/5a28853242af1c3a160c79426fe31256d5e37c1e Bug 1395358 - add support for session renewal This produces a new UserSession at each refresh, so tools that reload on sign-in need to be reworked to handle this. https://github.com/taskcluster/taskcluster-tools/commit/a793bf234447eba782fb5599f45df31374ee5107 Bug 1395358 - move all JSX out of AuthController
This is landed, just waiting a bit to enable it.
landed and shipped
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: Login → Services
You need to log in before you can comment on or make changes to this bug.