You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: