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

Is the token_reviewer_jwt mandatory to authenticate client requests? #63

Closed
goplusgo opened this issue Jun 12, 2019 · 2 comments
Closed

Comments

@goplusgo
Copy link

In our Vault docker init script file, we only inject the kubernetes_ca_cert for the k8s config:

vault write auth/kubernetes/config kubernetes_host=$KUBERNETES_HOST kubernetes_ca_cert=@/vault/data/cert/k8cert.crt 

And it's able to authenticate the client with k8s. Is the token_reviewer_jwt still mandatory (which is present in almost all the official samples or demos)?

@rumenvasilev
Copy link

It is not mandatory as stated in the official docs: https://www.vaultproject.io/api/auth/kubernetes/index.html#token_reviewer_jwt

...If not set the JWT used for login will be used to access the API.

@tomhjp
Copy link
Contributor

tomhjp commented Mar 30, 2022

Yep, if not set, it will either use the pod's own service account if Vault is in the k8s cluster, or it will use the client's token.

Full details here.

If not set, the local service account token is used if running in a Kubernetes pod, otherwise the JWT submitted in the login payload will be used to access the Kubernetes TokenReview API.

@tomhjp tomhjp closed this as completed Mar 30, 2022
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

3 participants