-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup unused applications in auth0 #519
Comments
Mmm... interesting... maybe this is the result of multiple deployments that somehow are generating dupe apps? |
The default per_page limit was 50 items, so we were not getting returned clients past 50, and recreating them on each deploy Ref #519
I was thinking about writing a helper script to tackle the cleanup of Auth0 apps today, the process would look like the following:
I had trouble figuring out from the deployer how to set up the connection to Auth0 though 😕 |
Thanks for looking into this, @sgibson91! infrastructure/deployer/auth.py Line 16 in fab3dc3
I hope that is helpful in getting you started! |
Huh, I must have run into an intermittent error on the API server as my draft script is working now 😄 |
I have opened #769 |
Is this now finished since #769 is merged? |
Actually, seeing the Wageningen app reminded me that that script only copes with duplicated apps, not apps that are unused because the hubs that generated them no longer exist. At the minimum, we need to add a checkpoint to the decommission hub issue template to manually remove the Auth0 (or GitHub) app when removing a hub. But cleaning the remaining apps up now probably requires a more manual approach. |
I updated the issue template in this PR #784 |
For future readers, we no longer use Auth0. |
Our auth0 account has a limit of 100 applications, and we're almost at the limit. There are a lot of unused applications there, because we changed naming schemes once. There's also some duplicates, and I'm not sure why.
In reality, we have way fewer than 100 applications. We need to clean this up.
TODO
The text was updated successfully, but these errors were encountered: