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

Vault UI does not reveal the value if the secret key contains a "." #8005

Closed
macplady opened this issue Dec 11, 2019 · 1 comment
Closed
Labels
bug Used to indicate a potential bug ui

Comments

@macplady
Copy link

Describe the bug
In the Vault UI, when you want to reveal the value of a key in the key/value secrets, it does not display any value if the key has a "." in it. The value stays blank, although there is a value for the key if you switch to json view.

To Reproduce
Steps to reproduce the behavior:

  1. Log in to Vault UI
  2. Navigate to a secret (or create a new one)
  3. Press "Edit secret"
  4. Enter a key with a "." like: my.key
  5. Enter any value for the key like: myValue
  6. Click Add and Save
  7. Press on the eye-icon next to the newly created key.
  8. The dots next to the eye-icon disapear, but no value gets displayed

Expected behavior
I expect to see the value for the key. From the example above, that would be "myValue".

Environment:

  • Vault Server Version: 1.3.0
  • Server Operating System/Architecture: RedHat OpenShift Container Platform 3.11

Vault server configuration file(s):

api_addr = "https://vault:8200" 

storage "consul" {
  address = "127.0.0.1:8500"
  token   = "xxxxxxxx"
}

listener "tcp" {
  address = "0.0.0.0:8200"
  tls_disable = "false"
  tls_cert_file = "/opt/vault/config/vault.cer"
  tls_key_file = "/opt/vault/config/vault.key"
}

telemetry {
  disable_hostname = true
  statsd_address = "localhost:9125"
}

disable_mlock = true

ui = true

log_level = "info"

Additional context
image

@michelvocks michelvocks added bug Used to indicate a potential bug ui version/1.3.x labels Dec 11, 2019
@michelvocks
Copy link
Contributor

Hi @macplady!

Thank you for your bug report!
This bug is known and has been fixed with #7926. It should be included in the next version.

Thanks again!

Cheers,
Michel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Used to indicate a potential bug ui
Projects
None yet
Development

No branches or pull requests

2 participants