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

Backport of Add possibility to decode generated encoded root token to api into release/1.13.x #20666

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #20595 to be assessed for backporting due to the inclusion of the label backport/1.13.x.

The below text is copied from the body of the original PR.


solves #5236 (closed)

this makes it possible to get a root token completely using the API by adding the possibility to decode the generated encoded root token at /v1/sys/decode-token

I think it's a good thing if the API supports the same things as the cli (here vault itself).


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/add-possibility-to-decode-token-to-api/oddly-ace-bear branch from 2240fb0 to e12b39f Compare May 18, 2023 19:18
@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/add-possibility-to-decode-token-to-api/oddly-ace-bear branch from a13e374 to eec481f Compare May 18, 2023 19:18
@ncabatoff ncabatoff enabled auto-merge (squash) May 18, 2023 19:19
@ncabatoff ncabatoff merged commit 6e7da68 into release/1.13.x May 18, 2023
@ncabatoff ncabatoff deleted the backport/add-possibility-to-decode-token-to-api/oddly-ace-bear branch May 18, 2023 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants