Article version: Enterprise Server 2.20
About SSH certificate authorities
With an SSH certificate authority, your organization or enterprise account can provide SSH certificates that members can use to access your resources with Git.
Support for SSH certificate authorities is available with GitHub Enterprise Cloud and GitHub Enterprise Server 2.19+. For more information, see "GitHub's products."
An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members with signed SSH certificates, you can add the CA to your enterprise account or organization to allow organization members to use their certificates to access organization resources. For more information, see "Managing your organization's SSH certificate authorities."
After you add an SSH CA to your organization or enterprise account, you can use the CA to sign client SSH certificates for organization members. Organization members can use the signed certificates to access your organization's repositories (and only your organization's repositories) with Git. You can require that members use SSH certificates to access organization resources.
For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on GitHub Enterprise. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised.
When you issue each certificate, you must include an extension that specifies which GitHub Enterprise user the certificate is for. For example, you can use OpenSSH's
ssh-keygen command, replacing KEY-IDENTITY with your key identity and USERNAME with a GitHub Enterprise username:
$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:email@example.com=USERNAME ./user-key.pub
To issue a certificate for someone who has different usernames for GitHub Enterprise Server and GitHub Enterprise Cloud, you can include two login extensions.
$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:firstname.lastname@example.org=CLOUD-USERNAME extension:login@HOSTNAME=SERVER-USERNAME ./user-key.pub
You can restrict the IP addresses from which an organization member can access your organization's resources by using a
source-address extension. The extension accepts a specific IP address or a range of IP addresses using CIDR notation. You can specify multiple addresses or ranges by separating the values with commas. For more information, see "Classless Inter-Domain Routing" on Wikipedia.
$ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:email@example.com=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub
Organization members can use their signed certificates for authentication even if you've enforced SAML single sign-on. Unless you make SSH certificates a requirement, organization members can continue to use other means of authentication to access your organization's resources with Git, including their username and password, personal access tokens, and their own SSH keys.
To prevent authentication errors, organization members should use a special URL that includes the organization ID to clone repositories using signed certificates. Anyone with read access to the repository can find this URL on the repository page. For more information, see "Cloning a repository."