Introduce jwt Issued At

If time drift occurs between the identity provider and the Hashi Vault, authentication will fail.  This is resolved by introducing a param to specify the number of seconds in the past for the jwt issued date
This commit is contained in:
Keith Murry 2024-02-12 13:10:18 -06:00
parent 9f522b8598
commit 2c6158aeef
3 changed files with 11 additions and 4 deletions

View file

@ -232,7 +232,7 @@ with:
You can configure trust between your own OIDC Provider and Vault
with the JWT auth method. Provide a `role` & `jwtPrivateKey` parameters,
additionally you can pass `jwtKeyPassword` & `jwtTtl` parameters
additionally you can pass `jwtKeyPassword`, `jwtTtl`, & `jwtIat` parameters.
```yaml
with:
@ -243,6 +243,7 @@ with:
jwtPrivateKey: ${{ secrets.JWT_PRIVATE_KEY }}
jwtKeyPassword: ${{ secrets.JWT_KEY_PASS }}
jwtTtl: 3600 # 1 hour, default value
jwtIat: 60 # 1 min, default value. Negative int postdates
```
### Kubernetes