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

Set Managed Namespace in Vault Config File #11347

Open
lucymhdavies opened this issue Apr 13, 2021 · 0 comments
Open

Set Managed Namespace in Vault Config File #11347

lucymhdavies opened this issue Apr 13, 2021 · 0 comments

Comments

@lucymhdavies
Copy link
Contributor

lucymhdavies commented Apr 13, 2021

Is your feature request related to a problem? Please describe.
#10588 looks to be a useful feature, and I suspect I've seen it in practice in my personal single-node HCP Vault:
image

However, to enable this requires setting a feature flag with sys/internal/ui/feature-flags.

This (presumably) would apply to the entire cluster including downstream enterprise performance replica clusters.

Additionally, that PR does not appear to add any documentation, and I could not find any on the https://www.vaultproject.io/ site.

Describe the solution you'd like
In our use-case, we have a performance replica cluster, to which we only replicate one namespace.
So this "automatically set namespace via feature flag" seems super useful, but the limitation that it would seemingly apply to all (replicated) clusters makes the current implementation not ideal.

Being able to set this in the Vault config file instead would allow us to set this flag only for our performance replica cluster.

Describe alternatives you've considered
For now, the URL we give to the users of this replica vault is something like:
https://child-namespace.vault.fancycorp.io/ui/vault/auth?namespace=child%namespace
This will pre-populate the namespace textbox.

But a solution where we just give our users the URL https://child-namespace.vault.fancycorp.io would be better.

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

No branches or pull requests

2 participants