Backport of fix: add AccessorID property to PUT token request into release/1.15.x #16662
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #16660 to be assessed for backporting due to the inclusion of the label backport/1.15.
The below text is copied from the body of the original PR.
Description
Triggering saving of token responds with 'Token Accessor ID in URL and payload do not match' error.
The reason is the AccessorID property has not been included to requestBody. there might be some changes on backend side, which updated requestBody structure to include AccessorID for token PUT endpoint.
Testing & Reproduction steps
Screen.Recording.2023-03-16.at.3.40.58.PM.mov
Testing & Reproduction steps
make ui-docker
to build the ui imagemake dev-docker
https://github.com/WenInCode/consul-setup
consul-setup
repo go to thesetups/peering directory
docker-compose up
yarn setup:peerings
Links
https://hashicorp.atlassian.net/browse/CC-4515
PR Checklist
Overview of commits