@@ -79,9 +79,9 @@ See [Examples](#examples) for more examples.
7979 ` ` `
8080
8181- `audience` : (Optional) The value for the audience (`aud`) parameter in the
82- generated GitHub Actions OIDC token. At present, the only valid value is
83- ` "sigstore" ` , but this variable exists in case custom values are permitted
84- in the future. The default value is `"sigstore"` .
82+ generated GitHub Actions OIDC token. This value defaults to the value of
83+ ` workload_identity_provider ` , which is also the default value Google Cloud
84+ expects for the audience parameter on the token .
8585
8686- `create_credentials_file` : (Optional) If true, the action will securely
8787 generate a credentials file which can be used for authentication via gcloud
@@ -331,23 +331,20 @@ the [gcloud][gcloud] command-line tool.
331331 --workload-identity-pool="my-pool" \
332332 --display-name="Demo provider" \
333333 --attribute-mapping="google.subject=assertion.sub,attribute.actor=assertion.actor,attribute.aud=assertion.aud" \
334- --issuer-uri="https://vstoken.actions.githubusercontent.com" \
335- --allowed-audiences="sigstore"
334+ --issuer-uri="https://vstoken.actions.githubusercontent.com"
336335 ` ` `
337336
338- - The audience of "sigstore" is currently the only value GitHub allows.
339- - The attribute mappings map claims in the GitHub Actions JWT to
340- assertions you can make about the request (like the repository or GitHub
341- username of the principal invoking the GitHub Action). These can be used
342- to further restrict the authentication using `--attribute-condition`
343- flags.
337+ The attribute mappings map claims in the GitHub Actions JWT to assertions
338+ you can make about the request (like the repository or GitHub username of
339+ the principal invoking the GitHub Action). These can be used to further
340+ restrict the authentication using `--attribute-condition` flags.
344341
345- For example, you can map the attribute repository values (which can be
346- used later to restrict the authentication to specific repositories) :
342+ For example, you can map the attribute repository values (which can be used
343+ later to restrict the authentication to specific repositories) :
347344
348- ` ` ` sh
349- --attribute-mapping="google.subject=assertion.sub,attribute.repository=assertion.repository"
350- ` ` `
345+ ` ` ` sh
346+ --attribute-mapping="google.subject=assertion.sub,attribute.repository=assertion.repository"
347+ ` ` `
351348
3523491. Allow authentications from the Workload Identity Provider to impersonate the
353350 Service Account created above :
@@ -389,7 +386,7 @@ Here is a sample GitHub Token for reference for attribute mappings:
389386{
390387 "jti": "...",
391388 "sub": "repo:username/reponame:ref:refs/heads/master",
392- "aud": "sigstore ",
389+ "aud": "https://iam.googleapis.com/projects/123456789/locations/global/workloadIdentityPools/my-pool/providers/my-provider ",
393390 "ref": "refs/heads/master",
394391 "sha": "d11880f4f451ee35192135525dc974c56a3c1b28",
395392 "repository": "username/reponame",
0 commit comments