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

integration with AWS Secret Manager for api-keys #5047

Open
bcollard opened this issue Jul 19, 2021 · 1 comment
Open

integration with AWS Secret Manager for api-keys #5047

bcollard opened this issue Jul 19, 2021 · 1 comment

Comments

@bcollard
Copy link
Contributor

Basically, what we’re looking for is a way to validate different API keys on the same route without saving all keys statically in k8s (as k8s secrets). What we would like to achieve is API key validation based on a given header (e.g. tenant header).

Example:

  • A Client sends a request with two headers: tenant (e.g. tenant-x) and api-key.
  • Gloo reaches to a secret manager (i.e. AWS secrets manager) and seeks a secret containing the api-key for tenant-x.
  • Gloo compares the secret sent by the client with the one it fetched from the secret manager.
@bcollard bcollard added the Type: Enhancement New feature or request label Jul 19, 2021
@jon-walton
Copy link
Contributor

@bcollard and azure key vault, if possible

the resulting tenant / api-key would need caching for x seconds

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

No branches or pull requests

3 participants