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.

Sign up for GitHub

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

Jump to bottom

Introduce limited permission service account #179

Open
1 task done
pauljohanneskraft opened this issue Nov 7, 2024 · 0 comments · May be fixed by #184
Open
1 task done

Introduce limited permission service account #179

pauljohanneskraft opened this issue Nov 7, 2024 · 0 comments · May be fixed by #184
Labels
enhancement New feature or request

Comments

@pauljohanneskraft
Copy link
Collaborator

Problem

Currently, we only use a single service account with elevated privileges for all functions.

Solution

We should investigate, which functions ultimately make use of the elevated privileges and assign the limited service account to all others. We should aim to only assign the elevated privileges to blocking functions.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct and Contributing Guidelines
@pauljohanneskraft pauljohanneskraft added the enhancement New feature or request label Nov 7, 2024
@pauljohanneskraft pauljohanneskraft linked a pull request Nov 11, 2024 that will close this issue
Introduce default and privileged service accounts #184
Draft
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
ENGAGE-HF Planning Board
Status: No status
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Introduce default and privileged service accounts StanfordBDHG/ENGAGE-HF-Firebase
1 participant
@pauljohanneskraft