Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Commit

Permalink
Update github.md
Browse files Browse the repository at this point in the history
  • Loading branch information
EronWright authored May 14, 2024
1 parent d56ed5a commit b6b5e23
Showing 1 changed file with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ menu:
weight: 1
---

This document outlines the steps required to configure Pulumi to accept Github id_tokens to be exchanged by Organization access tokens
This document outlines the steps required to configure Pulumi to accept Github id_tokens to be exchanged by Organization access tokens.

## Prerequisites

Expand All @@ -27,12 +27,12 @@ Please note that this guide provides step-by-step instructions based on the offi
![Register Github](../register-github.png)
1. Submit the form

## Conrigure the Authorization Policies
## Configure the Authorization Policies

1. Click on the issuer name
1. Change the policy decision to `Allow`
1. Change the token type to `Organization`
1. Add a new rule and configure it to verify the token audience to match your github organization url: `aud: https://github.com/octo-org`. For further information about Github token claims refer to the [official Github documentation](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#understanding-the-oidc-token).
1. Add a new rule and configure it to allow calls from your repository: `repository: octo-org/octo-repo`. For further information about Github token claims refer to the [official Github documentation](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#understanding-the-oidc-token).
![Github policy example](../github-policies.png)
1. Click on update

Expand Down

0 comments on commit b6b5e23

Please sign in to comment.