actions/auth
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

chore: document clock skew issue

Browse Source
This commit is contained in:
Seth Vargo 2022-05-16 09:59:39 -04:00
parent a1f1aca0d6
commit cf96743e5a
No known key found for this signature in database
GPG Key ID: 9C01CC8AB5D3F179
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/TROUBLESHOOTING.md
View File

@ -101,6 +101,21 @@ with the Google Cloud IAM team][iam-feedback]. The only mitigation is to use
shorter repo names or shorter branch names. shorter repo names or shorter branch names.
## Token lifetime cannot exceed 1 hour
If you get an error like:
```text
The access token lifetime cannot exceed 3600 seconds.
```
it means that there is likely clock skew between where you are running the
`auth` GitHub Action and Google's servers. You can either install and configure
ntp pointed at time.google.com, or adjust the `access_token_lifetime` value to
something less than `3600s` to allow for clock skew (`3300s` would allow for 5
minutes of clock skew).
## Dirty git or bundled credentials ## Dirty git or bundled credentials
By default, the `auth` action exports credentials to the current workspace so By default, the `auth` action exports credentials to the current workspace so