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 Pass encodeBase64 param to transit-key-actions into release/1.13.x #19465

Conversation

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

Backport

This PR is auto-generated from #19429 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.


A fix for the GH Issue here.

We missed passing the encodeBase64 param to the doSubmit action on hmac.hbs. You can see from other transit-key-action forms that show this option they pass this param in the hash to this action.

Added test coverage with minimal changes so the fix can be backported.

The checkbox under codemirror was the checkbox in question.
image


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/ui/VAULT-14109/HMAC-BASE64-BUG/willingly-valid-dog branch 2 times, most recently from 85fbf6a to c07f7b6 Compare March 6, 2023 18:29
@Monkeychip Monkeychip enabled auto-merge (squash) March 6, 2023 22:25
@Monkeychip Monkeychip added this to the 1.13.0 milestone Mar 6, 2023
@Monkeychip Monkeychip disabled auto-merge March 6, 2023 22:26
@anwittin anwittin modified the milestones: 1.13.0, 1.13.1 Mar 7, 2023
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