Hint to enable Single Sign-on for access token

[OutdatedVersion]

Select Topic Area

Product Feedback

Body

Hi! Our team is running into friction authorizing PATs for Single sign-on with GitHub Enterprise Cloud.

We see this occur in two cases:

• Creating a token
  • Not as common
  • Generally people are following our onboarding documentation which covers allowing access to our organization.
• Regenerating a token
  • Fairly common
  • Generally people head straight to the token page, see "Expired on X", and regenerate the token. This circumvents our documentation generating support work for internal teams if someone forgets to authenticate their new token.

I'm hoping something could be added on GitHub's side to help out.

Note: Use of classic access tokens (required for GitHub Packages access) is assumed as fine-grained access tokens have an explicit ownership model.

Ideas

1. A warning reminding people to reauthorize their token during regeneration. A more grounded approach as the regeneration flow doesn't change
   

2. A button to reauthorize their token during regeneration
   

Similar discussions

I looked through results for "enable sso", "sso pat", and "saml" only finding one similar, distinct, discussion: https://github.com/orgs/community/discussions/28502.