jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Add enterprise allow list considerations for SSH / PAT authorization (#56709)

Browse Source 
Co-authored-by: Justin Alex <1155821+jusuchin85@users.noreply.github.com>
This commit is contained in:
bss-mc
2025-07-22 08:24:17 -07:00
committed by GitHub
parent 50a5314981
commit e47f382f3c
2 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
content/authentication/authenticating-with-single-sign-on/authorizing-a-personal-access-token-for-use-with-single-sign-on.md
View File

@@ -29,6 +29,9 @@ You must authorize your {% data variables.product.pat_v1 %} after creation befor
1. In the dropdown menu, to the right of the organization you'd like to authorize the token for, click **Authorize**.
> [!NOTE]
> When authorizing a {% data variables.product.pat_v1 %} for use within an organization that belongs to an enterprise which has both an IP allow list and single sign-on enabled at the enterprise level, your IP must also be allowed at the enterprise level. See [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list).
## Further reading
* [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)

3
content/authentication/authenticating-with-single-sign-on/authorizing-an-ssh-key-for-use-with-single-sign-on.md
View File

@@ -37,6 +37,9 @@ You do not need to authorize SSH certificates signed by your organization's SSH
![Screenshot of the "Authentication Keys" section. Next to a key, a dropdown menu, labeled "Configure SSO," is outlined in orange.](/assets/images/help/settings/ssh-sso-button.png)
1. In the dropdown menu, to the right of the organization you'd like to authorize the SSH key for, click **Authorize**.
> [!NOTE]
> When authorizing an SSH key for use within an organization that belongs to an enterprise which has both an IP allow list and single sign-on enabled at the enterprise level, your IP must also be allowed at the enterprise level. See [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list).
## Further reading
* [AUTOTITLE](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)