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
Copy file name to clipboardExpand all lines: content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-aws.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,6 +70,17 @@ Edit the trust policy, adding the `sub` field to the validation conditions. For
70
70
}
71
71
```
72
72
73
+
For repositories created after July 15, 2026, or that have opted in to immutable subject claims, the `sub` claim includes immutable owner and repository IDs (not available on {% data variables.product.prodname_ghe_server %}). Make sure your trust policy matches the format your repository uses. For more information, see [AUTOTITLE](/actions/reference/openid-connect-reference#immutable-subject-claims).
If you use a workflow with an environment, the `sub` field must reference the environment name: `repo:ORG-NAME/REPO-NAME:environment:ENVIRONMENT-NAME`. For more information, see [AUTOTITLE](/actions/reference/openid-connect-reference#filtering-for-a-specific-environment).
74
85
75
86
{% data reusables.actions.oidc-deployment-protection-rules %}
Copy file name to clipboardExpand all lines: content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-azure.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,8 @@ This guide gives an overview of how to configure Azure to trust {% data variable
32
32
33
33
{% data reusables.actions.oidc-on-ghecom %}
34
34
35
+
For repositories created after July 15, 2026, and repository renames or transfers after that date, use an immutable default OIDC `sub` claim that includes owner and repository IDs (not available on {% data variables.product.prodname_ghe_server %}). Existing repositories keep the previous format unless they opt in. For more information, see [AUTOTITLE](/actions/reference/openid-connect-reference#immutable-subject-claims).
36
+
35
37
{% ifversion ghes %}
36
38
{% data reusables.actions.oidc-endpoints %}
37
39
<!-- This note is indented to align with the above reusable. -->
Copy file name to clipboardExpand all lines: content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-google-cloud-platform.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,8 @@ This guide gives an overview of how to configure GCP to trust {% data variables.
31
31
32
32
{% data reusables.actions.oidc-on-ghecom %}
33
33
34
+
For repositories created after July 15, 2026, and repository renames or transfers after that date, use an immutable default OIDC `sub` claim that includes owner and repository IDs (not available on {% data variables.product.prodname_ghe_server %}). Existing repositories keep the previous format unless they opt in. For more information, see [AUTOTITLE](/actions/reference/openid-connect-reference#immutable-subject-claims).
35
+
34
36
{% ifversion ghes %}
35
37
{% data reusables.actions.oidc-endpoints %}
36
38
<!-- This note is indented to align with the above reusable. -->
0 commit comments