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

Impossible to use refresh_token #154

Open
Gauth-code opened this issue Nov 13, 2024 · 1 comment
Open

Impossible to use refresh_token #154

Gauth-code opened this issue Nov 13, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Gauth-code
Copy link

PROBLEM SUMMARY
Impossible to use refresh_token and refresh_token_2 in command : vault write venafi-pki/venafi/tpp

STEPS TO REPRODUCE
vault write venafi-pki/venafi/tpp
url="https://tpp.venafi.example"
access_token="tn1PwE1QTZorXmvnTowSyA=="
refresh_token="MGxV7DzNnclQi9CkJMCXCg=="
refresh_token_2="p0WTt3sDPbzm2BDIkoJROQ=="
zone="DevOps\HashiCorp Vault"

ACTUAL RESULTS
Code 400: Error
Error writing date to venafi-pki/venafi/tpp: error making API request
*unexpected status code on TPP Authorize. Status: 400 Bad Request

ENVIRONMENT DETAILS
I have Venafi 24.1.2 on-premise

COMMENTS/WORKAROUNDS
the same command works perfectly if I remove the refresh_token and refresh_token_2
vault write venafi-pki/venafi/tpp
url="https://tpp.venafi.example"
access_token="tn1PwE1QTZorXmvnTowSyA=="
zone="DevOps\HashiCorp Vault"

--> Success! Data written to : venafi-pki/venafi/tpp

@Gauth-code Gauth-code added the bug Something isn't working label Nov 13, 2024
@arunpm111
Copy link

I noticed this same error when the client_id had mismatch with default value configured in this plugin.
it was fixed by overriding client_id by passing correct value from tpp in vault write command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants