In the latest (and final?) iteration of sign-in, we are no longer supporting the auth0-specific, audience-based federated login approach that treeherder, treestatus, tooltool, and https://bugzilla-management-dashboard.netlify.com/ use.

Instead, we'll be switching to an approach based on the existing client creator following roughly the flow we use for the command-line taskcluster signin command.

This will likely need additional review from someone on the sec team, both before implementation (to make sure the design is sound) and after.

I'm going to start by writing up in detail the proposed plan, and getting some review from sec-focused people.

I wrote up a proposal here:
https://docs.google.com/document/d/1x2PZGXQZCPK5iOmPVBURxVtnLRSC1QxZ1ssZmwMPiDA/edit#

Hassan, before I shop this around, can you take a look and share your feedback?

Looks really good!

I sent an email seeking feedback on that proposal from the affected folks as well as AJ and Kang.

https://github.com/taskcluster/taskcluster/pull/1202

Third party login is now supported. Should we consider this resolved?

I think so!! Awesome!