Vault: Database and userpass configuration not available in web UI

[ghost]

Describe the bug
After enabling the Database secrets engine, or userpass auth engine they are greyed out in the web UI. You have to drop back to the CLI to manage users or configure a connection for a specific database plugin.

I am sure other options are missing but these were the two most obvious issues.

To Reproduce
Steps to reproduce the behavior:

1. With the web UI enabled turn on userpass or database engines
2. Observe they are greyed out and unusable via the web

Expected behavior
The full configuration options should be available via the web interface similar to the CLI for users who prefer that or want to learn the product easier.

Environment:

• Vault Server Version (retrieve with vault status): newest
• Vault CLI Version (retrieve with vault version): newest
• Server Operating System/Architecture: not relevant

Vault server configuration file(s):

config not relevant here

Additional context
Can the documentation also be clarified about any other limitations of the web UI?

[daveadams]

Looks like this is a specific case of the feature request in #6067

[nesl247]

Just ran into this as well. It would also make it a lot easier if users could request their credentials from the UI rather than having to install the CLI.

[ademariag]

Also run into this. It was my main reason to install vault. Hope someone can work on this soon

[forestoden]

Any update on this?

[surfd4wg]

Having the same issue. Is there an update ?
Vault 1.5.0

[aphorise]

I suspect that the wider issue is the number of 'database' back-ends that are supported by default as well as the fact that each are with their own configuration-view and validation that are not common among the listed eleven (11) on secret/databases not to mention other custom database plugin.

I think the entailed effort with each might be more than obvious. Perhaps a better approach may be to start with two of the most common databases and thereafter the community might help with the implementation of others?

[ademariag]

I suspect that the wider issue is the number of 'database' back-ends that are supported by default as well as the fact that each are with their own configuration-view and validation that are not common among the listed eleven (11) on secret/databases not to mention other custom database plugin.

I think it would also be very valuable to get started to just enable fetching the credentials (which should be the same across all backends) rather than aim to configure the plugins, as I suggested in https://github.com/hashicorp/vault/issues/8013