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.

Sign up for GitHub

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

Jump to bottom

[BUG] If the token is not set in VaultConfig, it will not be set automatically after calling .auth().loginByKubernetes() #60

Open
trend-jeff-chu opened this issue Dec 15, 2023 · 0 comments
Open

[BUG] If the token is not set in VaultConfig, it will not be set automatically after calling .auth().loginByKubernetes() #60

trend-jeff-chu opened this issue Dec 15, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@trend-jeff-chu
Copy link

Describe the bug
I am not sure whether I implement it correctly, here is what I found:
If the token is not set in VaultConfig (either by specifying explicitly by calling .token("<my_token>"), or getting from environment variable VAULT_TOKEN),
it will not be set automatically after calling .auth().loginByKubernetes("<role>", "<jwt>").
Therefore, it will encounter 403 http error when calling logical().read(xxx)
@trend-jeff-chu trend-jeff-chu added the bug Something isn't working label Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@trend-jeff-chu