-
Notifications
You must be signed in to change notification settings - Fork 241
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
POST AuthV4 #5666
POST AuthV4 #5666
Conversation
Hello williamlardier,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
6d77ee7
to
ee154ec
Compare
ee154ec
to
055f9f4
Compare
/approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-557. Goodbye williamlardier. The following options are set: approve |
Bump vaultclient, this will use POST by default when issuing AuthV4 internal requests (verifySignatureV4) with a security token (unbounded) or request contexts (same, but here it authorizes as well).
Fixes issues when any of those is too long for the backend to handle (as nodejs imposes max lengths for the http GET requests).
-> No new branch for now, as there is no breaking change in this service, but only vaultclient...