Skip to content
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

Fix leaked Firebase Admin SDK Key... again... #37

Closed
budak7273 opened this issue Oct 19, 2022 · 2 comments
Closed

Fix leaked Firebase Admin SDK Key... again... #37

budak7273 opened this issue Oct 19, 2022 · 2 comments
Assignees

Comments

@budak7273
Copy link
Member

Was in this commit: https://github.com/AutomatingSciencePipeline/Monorepo/blob/989eedd7ada8a44e872b7705c83d46ddeff78832/services/supabase/.env

We already revoked key and generated a new one (it's in the discord)

Attempted to add the .env file to the gitignore, but it did not work because the previous team had already committed their .env files. Deleted the branch that introduced it right away, but that's not enough to fix it, so we regenerated the key as well.

We went through and made a PR that cleans up all old .env files and fixed the other mistakes in the gitignores.

This guide for cleaning it up: https://cloud.google.com/docs/security/compromised-credentials

This page is where to delete keys and regenerate new ones: https://console.cloud.google.com/iam-admin/serviceaccounts?project=gladosbase&supportedpurview=project

@budak7273
Copy link
Member Author

#38 should make this more difficult to cause again

@budak7273
Copy link
Member Author

Time spent ~45 minutes

@budak7273 budak7273 added this to the 10/20/2022 - Wk7 milestone Oct 19, 2022
@budak7273 budak7273 moved this from 👀 In review to ✅ Done in Task Board Oct 27, 2022
@budak7273 budak7273 self-assigned this Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

1 participant