Managing your organization's SSH certificate authorities

You can allow members to access your organization's repositories using SSH certificates you provide by adding an SSH CA to your organization. You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository. For more information, see "About SSH certificate authorities."

When you issue each client certificate, you must include an extension that specifies which GitHub AE user the certificate is for. For more information, see "About SSH certificate authorities."

Adding an SSH certificate authority

If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. For more information, see "About SSH certificate authorities."

1. In the top right corner of GitHub AE, click your profile photo, then click Your organizations.

   

2. Next to the organization, click Settings.

3. In the "Security" section of the sidebar, click Authentication security.

4. To the right of "SSH Certificate Authorities", click New CA.

5. Under "Key," paste your public SSH key.

6. Click Add CA.

7. Optionally, to require members to use SSH certificates, select Require SSH Certificates, then click Save.

   Note: When you require SSH certificates, the requirement does not apply to authorized OAuth Apps and GitHub Apps or to GitHub features such as GitHub Actions, which are trusted environments within the GitHub ecosystem.

Deleting an SSH certificate authority

1. In the top right corner of GitHub AE, click your profile photo, then click Your organizations.

   

2. Next to the organization, click Settings.

3. In the "Security" section of the sidebar, click Authentication security.

4. Under "SSH Certificate Authorities", to the right of the CA you want to delete, click Delete.

5. Read the warning, then click I understand, please delete this CA.