Skip to content

Commit f29a870

Browse files
authored
Merge pull request github#24046 from github/repo-sync
repo sync
2 parents 310c3bc + 6312d67 commit f29a870

File tree

2 files changed

+11
-1
lines changed

2 files changed

+11
-1
lines changed

content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -376,7 +376,7 @@ For example: `"sub": "repo:octo-org/octo-repo:environment:prod:job_workflow_ref:
376376

377377
#### Example: Granting access to a specific repository
378378

379-
This example template lets you grant cloud access to all the workflows in a specific repository, across all branches/tags and environments. To help improve security, combine this template with the custom issuer URL described in "[AUTOTITLE](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#customizing-the-token-url-for-an-enterprise)."
379+
This example template lets you grant cloud access to all the workflows in a specific repository, across all branches/tags and environments. {% ifversion ghec %}To further improve security, you can combine this template with a unique issuer URL for your enterprise, as described in "[Switching to a unique token URL](#switching-to-a-unique-token-url)."{% endif %}
380380

381381
{% data reusables.actions.use-request-body-api %}
382382

content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,15 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
4444
bound_issuer="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}" \
4545
oidc_discovery_url="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}"
4646
```
47+
48+
{% ifversion ghec %}
49+
{% note %}
50+
51+
**Note:** If a unique issuer URL for an enterprise was set using the REST API (as described in "[Switching to a unique token URL](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#switching-to-a-unique-token-url)"), the values for `bound_issuer` and `oidc_discover_url` must match that unique URL. For example, for an enterprise named `octocat` that uses the unique issuer URL, `bound_issuer` and `oidc_discovery_url` must be set to `https://token.actions.githubusercontent.com/octocat`.
52+
53+
{% endnote %}
54+
{% endif %}
55+
4756
2. Configure a policy that only grants access to the specific paths your workflows will use to retrieve secrets. For more advanced policies, see the HashiCorp Vault [Policies documentation](https://www.vaultproject.io/docs/concepts/policies).
4857

4958
```sh{:copy}
@@ -78,6 +87,7 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
7887
7988
For more information, see the HashiCorp Vault [documentation](https://www.vaultproject.io/docs/auth/jwt).
8089
90+
8191
## Updating your {% data variables.product.prodname_actions %} workflow
8292
8393
To update your workflows for OIDC, you will need to make two changes to your YAML:

0 commit comments

Comments
 (0)