English
Explore by product
Authentication
English
Authentication
Keeping your account and data secure→
To protect your personal information, you should keep both your account on your GitHub Enterprise Server instance and any associated data secure.
Securing your account with two-factor authentication (2FA)→
You can set up your account on your GitHub Enterprise Server instance to require an authentication code in addition to your password when you sign in.
Connecting to GitHub with SSH→
You can connect to GitHub Enterprise Server using the Secure Shell Protocol (SSH), which provides a secure channel over an unsecured network.
Troubleshooting SSH→
When using SSH to connect and authenticate to GitHub Enterprise Server, you may need to troubleshoot unexpected issues that may arise.
Managing commit signature verification→
You can sign your work locally using GPG or S/MIME. GitHub Enterprise Server will verify these signatures so other people will know that your commits come from a trusted source.
Troubleshooting commit signature verification→
You may need to troubleshoot unexpected issues that arise when signing commits locally for verification on GitHub Enterprise Server.
Help us make these docs great!
All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.
Make a contribution

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
