Skip to main content

This version of GitHub Enterprise Server was discontinued on 2023-09-25. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.

Sudo mode

To confirm access to your account before you perform a potentially sensitive action, your GitHub Enterprise Server instance prompts for authentication.

About sudo mode

To maintain the security of your account when you perform a potentially sensitive action on your GitHub Enterprise Server instance, you must authenticate even though you're already signed in. For example, GitHub considers the following actions sensitive because each action could allow a new person or system to access your account.

  • Modification of an associated email address
  • Authorization of a third-party application
  • Addition of a new SSH key
  • Creation of a PAT or application

After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. GitHub Enterprise Server has a two-hour session timeout period before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer.

Note: If your GitHub Enterprise Server instance uses an external authentication method like CAS or SAML SSO, you will not receive prompts to enter sudo mode. For more information, contact your site administrator.

"sudo" is a reference to a program on Unix systems, where the name is short for "superuser do." For more information, see sudo on Wikipedia.

Confirming access for sudo mode

To confirm access for sudo mode, you must authenticate with your password.

When prompted to authenticate for sudo mode, type your password, then click Confirm.