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

Transit Engine UI: HMAC algorithm selection is not applied. #4550

Closed
jboero opened this issue May 11, 2018 · 0 comments
Closed

Transit Engine UI: HMAC algorithm selection is not applied. #4550

jboero opened this issue May 11, 2018 · 0 comments
Labels
Milestone

Comments

@jboero
Copy link

jboero commented May 11, 2018

Environment:

  • Vault Version: >= 0.10.0+prem
  • Operating System/Architecture: Linux/Darwin (any)

In the Vault UI, Transit -> rsa-2048 key -> actions - HMAC.
Enter any text value and encode it to BASE64.
Select any algorithm (sha2-224, sha2-256, sha2-384, sha2-512) and submit.

Expected Behaviour:

A HMAC should be generated with the algorithm you selected.

Actual Behavior:

A HMAC is generated with sha2-256 no matter what algorithm you've selected. CLI and API function as expected, so this is likely a UI issue.

Steps to Reproduce:

Important Factoids:

References:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants