-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
vault cli -output-curl-string
does not include client cert info
#13376
Comments
About to submit another bug report and noticing the template is different... Not sure how I got to this. Let me know if you want it refactored into the actual bug report template. |
@bmendric This should be good to start, we'll let you know if we have questions. :) |
heatherezell
added
auth/cert
Authentication - certificates
core/cli
bug
Used to indicate a potential bug
labels
Dec 10, 2021
remilapeyre
added a commit
to remilapeyre/vault
that referenced
this issue
Jan 13, 2022
I did not write tests for this feature as -output-curl-string was not already tested and this is a simple change. Because the name of the certificates would be lost once loaded I added fields to Config to keep track of them. I did not add a public method for the user to set them explicitely as I don't think anyone would need this functionnality outside of the Vault CLI. Closes hashicorp#13376
Thanks for reporting this @bmendric, this was also affecting other commands like |
HridoyRoy
pushed a commit
that referenced
this issue
Jan 20, 2022
* Add support for client certificates to -output-curl-string I did not write tests for this feature as -output-curl-string was not already tested and this is a simple change. Because the name of the certificates would be lost once loaded I added fields to Config to keep track of them. I did not add a public method for the user to set them explicitely as I don't think anyone would need this functionnality outside of the Vault CLI. Closes #13376 * Add changelog * Add lock in ConfigureTLS
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment:
Expected Behavior:
Performing the following command:
vault login -method=cert -address=https://localhost:1234 -client-cert=client.crt -client-key=client.key -output-curl-string
should result in the curl command:
curl -X PUT -H "X-Vault-Request: true" -d '{"name":""}' --cert ./client.crt --key ./client.key https://localhost:1234/v1/auth/cert/login
Actual Behavior:
Performing the following command:
vault login -method=cert -address=https://localhost:1234 -client-cert=client.crt -client-key=client.key -output-curl-string
should result in the curl command:
curl -X PUT -H "X-Vault-Request: true" -d '{"name":""}' https://localhost:1234/v1/auth/cert/login
Steps to Reproduce:
See above commands; only need validly PEM encoded crt and key files to test
References:
The text was updated successfully, but these errors were encountered: