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

Provide a query parameter in UI to allow specifying mount in login UI #10140

Closed
shwuandwing opened this issue Oct 13, 2020 · 5 comments
Closed

Comments

@shwuandwing
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Today, the Vault login url can take a query parameter specifying the login method. e.g. https://vault.com/ui/vault/auth?with=jwt . This lets people write documentation and share links to the Vault UI that has the jwt as the login method populated. There is a query parameter to support prefilling the namespace as well for Enterprise.

We like a query parameter in the url to specify the mount path as well (for customers who create auth mounts at a custom path). Curently, we have to share a url to the with jwt specified but document to users to specify the mount path

Describe the solution you'd like
A query parameter to specify the mount path

@martincostello
Copy link

Similarly, I'd also like a query string parameter that can be used for the role name for a JWT/OpenID connection. Maybe there's scope to look at prefill parameters in general, rather than just specifically for adding mount path and this?

@remilapeyre
Copy link
Contributor

Hi, I opened a PR to fix this issue: #14988

@heatherezell
Copy link
Contributor

The linked PR was closed due to inactivity, so I wanted to come by and give a (slightly belated, apologies) update. Our engineers are planning on making some changes and improvement to the auth forms, which will hopefully help cover some of these pain points. We have linked this GitHub issue to our internal Jira tracking ticket, so if this gets closed, check the release notes to see what made it in. Thanks so much for your patience!

@marcportabellaclotet-mt

Any update on this topic?

@hellobontempo
Copy link
Contributor

hellobontempo commented Feb 19, 2025

Apologies for the delay here. This behavior actually already exists, admittedly the UX is confusing and we're working on improving the workflow as well as adding clear documentation.

  1. Tune the mount to have listing_visibility="unauth". This can be done using the CLI or UI (docs). This makes the custom path known to the web UI prior to authentication.
Image
  1. When tab is selected the with= query param designates the custom mount path
Image

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

Successfully merging a pull request may close this issue.

7 participants