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

Fetch config_token like a Kubernetes Secret from Vault #182

Open
AnirudhGargUC opened this issue Aug 8, 2023 · 1 comment
Open

Fetch config_token like a Kubernetes Secret from Vault #182

AnirudhGargUC opened this issue Aug 8, 2023 · 1 comment

Comments

@AnirudhGargUC
Copy link

Is it possible to fetch and populate this config_token created, as a kubernetes secret from Vault using External Secrets Operator?

Currently in my solution, I have hard-coded the token in the auth_url of ambassador Auth Service, has anyone fetched and used this as a variable somehow?
Need help populating this __token__ variable.

Current config :

apiVersion: getambassador.io/v3alpha1
kind: AuthService
metadata:
  name: authentication
spec:
  auth_service: external-auth-operator-dev-external-auth-server.external-auth-operator:80
  path_prefix: /ambassador/verify-params-url/%7B%22config_token%22%3A%22__token__22%7D
  allowed_request_headers:
  - "x-qotm-session"
  - "authorization"
  include_body:
    max_bytes: 4096
    allow_partial: true
  status_on_error:
    code: 503
@AnirudhGargUC AnirudhGargUC changed the title Fetch config_token like a Kubernetes Secret from from Vault Fetch config_token like a Kubernetes Secret from Vault Aug 8, 2023
@travisghansen
Copy link
Owner

travisghansen commented Aug 8, 2023

You can use server-side tokens: https://github.com/travisghansen/external-auth-server/blob/master/CONFIG_TOKENS.md#server-side-tokens

I think it would be pretty easy to add additional store types/adapters for either or both of k8s secrets and vault.

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

No branches or pull requests

2 participants