-
Notifications
You must be signed in to change notification settings - Fork 138
optional mount path for approle #292
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
Conversation
|
No test as I don't see custom path testing in |
|
Hello, is it possible to have a review please ? as the change is very small, it should be fast :) |
|
Hi there! We are definitely happy to take a look at this PR! However, our team has inherited this project and we are currently working on ironing out issues with the CI & automated tests. Once we have those fixed we'll be able to review the PRs and take changes. |
|
Hello, some news maybe ? |
|
Hi there |
Adds optional mount parameter to approle() method to support AppRole authentication against non-default mount points. Usage: # Default mount point Vault.auth.approle(role_id, secret_id) # Custom mount point Vault.auth.approle(role_id, secret_id, mount: "my-approle") The implementation uses an options hash (mount:) to maintain consistency with other auth methods like userpass and ldap, and to allow for future extensibility. Fully backward compatible - defaults to 'approle' mount. Changes: - Updated approle() to accept options hash with :mount parameter - Fixed deprecated JSON.fast_generate to JSON.generate - Added integration test for custom mount path - Added documentation examples for both default and custom mounts - Updated CHANGELOG Co-authored-by: Laurent Lafage <laurent.lafage@fr.clara.net>
Actually the path for an approle is fixed in code:"/v1/auth/approle/login".
This PR add the possibility to support customizable path, for example, "/v1/auth/my_approle/login"