1
0
mirror of synced 2025-12-19 18:10:59 -05:00
Files
docs/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md
Hector Alfaro 95e6f3d3ab Deprecate GHES 3.1 (#28798)
* add 3.1 to deprecated versions

* rewrite img src to use azure blob storage in archive script

Co-authored-by: rachmari <rachmari@users.noreply.github.com>

* remove static files for ghes 3.1

* remove liquid conditionals and content for ghes 3.1

* remove outdated hardware reqs reusable

* Fix liquid conditional uncaught by script

* Close liquid conditionals missed by script

* Apply @mattpollard's suggestions

Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>

Co-authored-by: rachmari <rachmari@users.noreply.github.com>
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
2022-07-11 21:17:09 +00:00

3.1 KiB

title, intro, permissions, redirect_from, versions, type, topics, shortTitle
title intro permissions redirect_from versions type topics shortTitle
Configuring built-in authentication When you use the default authentication method, all authentication details are stored on {% data variables.product.product_location %}. Site administrators can configure authentication for a {% data variables.product.product_name %} instance.
/enterprise/admin/user-management/using-built-in-authentication
/enterprise/admin/authentication/using-built-in-authentication
/admin/authentication/using-built-in-authentication
/enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication
/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication
ghes
*
how_to
Accounts
Authentication
Enterprise
Identity
Configure built-in authentication

About built-in authentication

By default, {% data variables.product.product_name %} uses built-in authentication. Each person creates a user account on {% data variables.product.product_location %} from an invitation or by signing up, and then authenticates with the credentials for the account to access your instance. Your {% data variables.product.product_name %} instance stores the authentication information for the account.

You can prevent unauthenticated people from creating new user accounts on your instance. For more information, see "Disabling unauthenticated sign-ups."

{% data reusables.enterprise_user_management.alternatively-enable-external-authentication %}

Configuring built-in authentication

{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} 4. Select Built in authentication. Select built-in authentication option

{% data reusables.enterprise_user_management.two_factor_auth_header %} {% data reusables.enterprise_user_management.2fa_is_available %}

Creating your account

Once your instance has been created, you'll need to create your own admin account.

  1. On the "Create Admin Account" page at http(s)://[hostname]/join, choose your username, password, and email address, then click Create an account. Create Admin Account {% data reusables.enterprise_site_admin_settings.sign-in %}

Next steps

After you configure built-in authentication and create your administrative account, you can invite people to create accounts and use your instance. For more information, see "Inviting people to use your instance."

Further reading