You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The loginByJwt method doesn't support a parameter to specify a different endpoint when sending the request to Vault after getting the JWT token, it always goes to a hardcoded endpoint:
This means, that the plugin is expecting to have any Vault auth methods to be mounted or configured at the default location.
In our scenario, we use the GCP method, but the mount point is configured to auth/gcp/company_name/login, therefore when using the plugin we always get a 403 response from Vault, as the request goes to auth/gcp/login.
Upstream changes
No response
The text was updated successfully, but these errors were encountered:
What feature do you want to see added?
The
loginByJwt
method doesn't support a parameter to specify a different endpoint when sending the request to Vault after getting the JWT token, it always goes to a hardcoded endpoint:https://github.com/BetterCloud/vault-java-driver/blob/900ffe9a47dced88484588b315803210e17b349a/src/main/java/com/bettercloud/vault/api/Auth.java#L1030-L1039
This means, that the plugin is expecting to have any Vault auth methods to be mounted or configured at the default location.
In our scenario, we use the GCP method, but the mount point is configured to
auth/gcp/company_name/login
, therefore when using the plugin we always get a 403 response from Vault, as the request goes toauth/gcp/login
.Upstream changes
No response
The text was updated successfully, but these errors were encountered: