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
feature request to add support for providing google JWTAccessToken through vault.
These tokens can be derived from service accounts that are a special token type used to authenticate against some certain google services. For more info, see AccessTokenCredentials
I put together a prototype of secret_type=jwt_access_token by directly copying the access_token implementation code, then adding an additional flag for audience:
Note: unlike #46, the bindings here makes sense since IAM policies need to be in place the last step. Essentially, this FR is equivalent to access_token flow that there now but is optimized for certain GCP services.
The text was updated successfully, but these errors were encountered:
feature request to add support for providing google
JWTAccessToken
through vault.These tokens can be derived from service accounts that are a special token type used to authenticate against some certain google services. For more info, see AccessTokenCredentials
I put together a prototype of
secret_type=jwt_access_token
by directly copying the access_token implementation code, then adding an additional flag for audience:https://github.com/salrashid123/vault-plugin-secrets-gcp/blob/master/README_oidc_jwt.md#run-jwt-access
secrets_jwt_access_token.go
jwtaccess.hcl
to define its capabilitiesjwtaccess
secret backwhich includes claims:
a user can then apply the token to a request:
Note: unlike #46, the
bindings
here makes sense since IAM policies need to be in place the last step. Essentially, this FR is equivalent toaccess_token
flow that there now but is optimized for certain GCP services.The text was updated successfully, but these errors were encountered: