Deploy an instanceInstall GitHub Enterprise Server on your platform of choice and configure SAML authentication.Start path
System overviewGitHub Enterprise Server is your organization's private copy of GitHub contained within a virtual appliance, hosted on premises or in the cloud, that you configure and control.
- 2How-to guide
Installing GitHub EnterpriseSystem administrators and operations and security specialists can install GitHub Enterprise Server.
- 3How-to guide
Accessing the management consoleYou can use the Management Console to manage virtual appliance settings such as the domain, authentication, and SSL.
- 4How-to guide
Configuring a hostnameWe recommend setting a hostname for your appliance instead of using a hard-coded IP address.
- 5How-to guide
Using SAMLSAML is an XML-based standard for authentication and authorization. GitHub Enterprise Server can act as a service provider (SP) with your internal SAML identity provider (IdP).
Site admin dashboardYou can use the site admin dashboard to manage users, organizations, and repositories in your enterprise directly in GitHub Enterprise Server.
Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.
Learn how to plan and implement a roll out of GitHub Actions in your enterprise.
Back up your developers' code and configure high availability (HA) to ensure the reliability of GitHub Enterprise Server in your environment.
Review network configuration and security features, and harden the instance running GitHub Enterprise Server to protect your enterprise's data.
Allow your developers to create, automate, customize, and execute powerful software development workflows for your GitHub Enterprise Server instance with GitHub Actions.
Improve the quality and security of your developers' code with GitHub Advanced Security.
Allowing built-in authentication for users outside your identity provider
You can configure built-in authentication to authenticate users who don't have access to your identity provider that uses LDAP, SAML, or CAS.
Changing authentication methods
You can change the way GitHub Enterprise Server authenticates with your existing accounts at any time.
CAS is a single sign-on (SSO) protocol for multiple web applications. A CAS user account does not take up a user license until the user signs in.
LDAP lets you authenticate GitHub Enterprise Server against your existing accounts and centrally manage repository access. LDAP is a popular application protocol for accessing and maintaining directory information services, and is one of the most common protocols used to integrate third-party software with large company user directories.
SAML is an XML-based standard for authentication and authorization. GitHub Enterprise Server can act as a service provider (SP) with your internal SAML identity provider (IdP).
Accessing the administrative shell (SSH)
SSH access allows you to run the GitHub Enterprise Server command line utilities to troubleshoot, run backups, and configure replication.
Accessing the management console
You can use the Management Console to manage virtual appliance settings such as the domain, authentication, and SSL.
Configuring a hostname
We recommend setting a hostname for your appliance instead of using a hard-coded IP address.