Hello! Thanks for all the great work on Auth0, it makes singing in as a MoCo employee very convenient.
I work on https://janitor.technology/ and we’d like to add MoCo-specific resources to our service (i.e. AWS container hosting + Azure Windows VM hosting, paid for by Mozilla for its employees working on Firefox and Servo).
Janitor already has a few OAuth2 integrations (GitHub and Bugzilla, both WIP) which can be enabled in your Janitor settings (but we’d also like to eventually offer “Sign in with GitHub/Bugzilla” buttons on the login page).
So we’d like to add a MoCo Auth0 integration, allowing MoCo employees to sign in with it and access MoCo-specific resources.
Could you please point us in the right direction? Specifically, we’d like to know:
- How to register https://janitor.technology/ as a MoCo Auth0 app (i.e. “Relying Party”?), in exchange for a
client_id
andclient_secret
? - Is the usual OAuth2 web flow supported, i.e. link user to an authorization URL like
https://auth.mozilla.auth0.com/login/oauth/authorize
(with paramsclient_id
,redirect_uri
,scope
andstate
), and then eventually they’re redirected to a URL likehttps://janitor.technology/login/moco-auth0/
(with paramsaccessToken
andrefreshToken
)? - Does OpenID Connect change many things to the usual OAuth2 web flow?