Simplify our authentication workflow by migrating all communities to CILogon authenticator and away from Auth0

[GeorgianaElena]

Context

As part of #967, we decided and implemented the infrastructure for using CILogon as the authenticator for the 2i2c hubs.

This was possible thanks to

• https://github.com/jupyterhub/oauthenticator
• the CILogon folks who offered a free trial of their admin API

The JupyterHub CILogon OAuthenticator is currently used by several hubs:

• ANU hub
• 2i2c demo hub
• cloudbank demo hub
• dask-staging

Proposal

I propose thinking a strategy to migrate all the hubs to using the CILogonOAuthenticator if we decide to do it.
Also, provide feedback and share our experience with the CILogon folks, possible though a blog post.

Updates and actions

This needs to happen first I believe

• https://github.com/2i2c-org/meta/issues/317

Also, checkout @choldgraf proposal here for a possible rollout process #967 (comment)

Relevant issues that are worth to be kept an eye on in this context:

• [CILogon] Allow specifying which domains should be allowed to login using a specific identity provider jupyterhub/oauthenticator#515
• [CILogon] Instructions for CILogon with Google OAuth use new Google API for oid, but CILogon uses an old OAuth API jupyterhub/oauthenticator#522
• Update Google authorization endpoint ncsa/oa4mp#45

[GeorgianaElena]

New oathenticator version released. See #1319 (comment) for details

[GeorgianaElena]

I will be closing this issue, since all of the action points have been done. We still need to remove the current setup for Auth0 from our infra, I believe. But we could open a new issue for that

[GeorgianaElena]

Actually, this is the issue that tracks the removal of Auth0. The tile was a bit confusing. Sorry about that

[yuvipanda]

100% I agree we should get rid of auth0 :)