Merge pull request #228 from tailscale/max/clarify-writable-auth_key-scope

README: clarify auth_key scope must be writable
This commit is contained in:
Max Coulombe 2025-11-10 09:48:04 -05:00 committed by GitHub
commit dea278bd44
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -17,7 +17,7 @@ Subsequent steps in the Action can then access nodes in your Tailnet.
oauth-client-id and oauth-secret are an [OAuth client][kb-oauth-clients]
for the tailnet to be accessed. We recommend storing these as
[GitHub Encrypted Secrets.](https://docs.github.com/en/actions/security-guides/encrypted-secrets)
OAuth clients used for this purpose must have the
OAuth clients used for this purpose must have the writable
[`auth_keys` scope.][kb-trust-credentials-scopes]
tags is a comma-separated list of one or more [Tags][kb-tags]
@ -49,7 +49,7 @@ permissions:
id-token: write # This is required for the tailscale action to request a JWT from GitHub
```
OIDC federated identity credentials used for this purpose must have the [`auth_keys` scope.][kb-trust-credentials-scopes]
OIDC federated identity credentials used for this purpose must have the writable [`auth_keys` scope.][kb-trust-credentials-scopes]
tags is a comma-separated list of one or more [Tags][kb-tags]
for the node. At least one tag is required: a federated identity is not associated