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

Astral needs a mechanism for determining whether a supplied token has the rights to perform a read operation #56

Closed
dave-gantenbein opened this issue Oct 22, 2024 · 2 comments · Fixed by #72
Assignees

Comments

@dave-gantenbein
Copy link
Contributor

dave-gantenbein commented Oct 22, 2024

Because Astral communicates with Vault using it's own identity token, we need to verify the upstream user identity has rights to read a secret.

  1. fetch policies for the upstream user
  2. validate that the KV policy is possessed by the user

For the MVP, the KV policy will be unique for each secret and only granted to the identity that created the secret. However, we will probably need to use groups in a future story.

@GeorgeJahad
Copy link
Collaborator

It seems like we need more info from the dallas team here.

@suprjinx
Copy link
Collaborator

suprjinx commented Nov 5, 2024

yes need more info -- particularly how group permissions should work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants