Skip to content

Commit e47f382

Browse files
bss-mcjusuchin85
andauthored
Add enterprise allow list considerations for SSH / PAT authorization (#56709)
Co-authored-by: Justin Alex <[email protected]>
1 parent 50a5314 commit e47f382

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,9 @@ You must authorize your {% data variables.product.pat_v1 %} after creation befor
2929

3030
1. In the dropdown menu, to the right of the organization you'd like to authorize the token for, click **Authorize**.
3131

32+
> [!NOTE]
33+
> 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).
34+
3235
## Further reading
3336

3437
* [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,9 @@ You do not need to authorize SSH certificates signed by your organization's SSH
3737
![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)
3838
1. In the dropdown menu, to the right of the organization you'd like to authorize the SSH key for, click **Authorize**.
3939

40+
> [!NOTE]
41+
> 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).
42+
4043
## Further reading
4144

4245
* [AUTOTITLE](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)

0 commit comments

Comments
 (0)