зеркало из https://github.com/github/docs.git
[Enterprise] Reduce usage of `{% data variables.location.product_location %}` (#52251)
This commit is contained in:
Sophie
GitHub
Родитель
36635c6d2a
Коммит
bb58931d4a
|
|
@ -20,8 +20,6 @@ topics:
|
|||
shortTitle: Configure GitHub Pages
|
||||
---
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
## Enabling public sites for {% data variables.product.prodname_pages %}
|
||||
|
||||
If private mode is enabled on your enterprise, the public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites.
|
||||
|
|
@ -48,10 +46,6 @@ If subdomain isolation is disabled for your enterprise, you should also disable
|
|||
1. Deselect **Enable Pages**.
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
## Configuring {% data variables.product.prodname_pages %} response headers for your enterprise
|
||||
|
||||
You can add or override response headers for {% data variables.product.prodname_pages %} sites hosted by {% data variables.location.product_location %}.
|
||||
|
|
@ -70,11 +64,6 @@ You can add or override response headers for {% data variables.product.prodname_
|
|||
1. Click **Add headers**.
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
## Further reading
|
||||
|
||||
* "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-private-mode)"
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ redirect_from:
|
|||
- /admin/user-management/customizing-user-messages-on-your-instance
|
||||
- /admin/user-management/customizing-user-messages-for-your-enterprise
|
||||
- /admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise
|
||||
intro: 'You can create custom messages that users will see on {% data variables.location.product_location %}.'
|
||||
intro: 'You can create custom messages that users will see on {% data variables.product.github %}.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
|
|
|
|||
|
|
@ -111,13 +111,13 @@ The "Deployment" column groups users by the type of deployment they are using. F
|
|||
|
||||
## Viewing members' email addresses
|
||||
|
||||
You may be able to view the email addresses for members of your enterprise on either {% data variables.location.product_location %} or an external identity system. The visibility of the email addresses depends on your enterprise's authentication method, domains, and potentially the member's user profile configuration.
|
||||
You may be able to view the email addresses for members of your enterprise on either {% data variables.product.github %} or an external identity system. The visibility of the email addresses depends on your enterprise's authentication method, domains, and potentially the member's user profile configuration.
|
||||
|
||||
* If you use {% data variables.product.prodname_emus %} and the `NameID` for your SAML configuration is an email address, you can view the `NameID` for each of your enterprise members.
|
||||
|
||||
* If you verify a domain for your enterprise, you can view members' email addresses for the verified domain. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
|
||||
|
||||
* If you don't use {% data variables.product.prodname_emus %}, and you also don't configure SAML single sign-on (SSO), members access your enterprise's resources on {% data variables.location.product_location %} solely using a personal account. {% data reusables.saml.personal-accounts-determine-email-visibility %}
|
||||
* If you don't use {% data variables.product.prodname_emus %}, and you also don't configure SAML single sign-on (SSO), members access your enterprise's resources on {% data variables.product.github %} solely using a personal account. {% data reusables.saml.personal-accounts-determine-email-visibility %}
|
||||
|
||||
If you use {% data variables.product.prodname_emus %}, verify a domain, or configure SAML SSO for your enterprise, you may be able to view the email addresses in one or more of the following ways.
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ If your enterprise uses **personal accounts**, you must follow a different proce
|
|||
|
||||
## About SAML SSO for {% data variables.product.prodname_emus %}
|
||||
|
||||
With {% data variables.product.prodname_emus %}, access to your enterprise's resources on {% data variables.location.product_location %} must be authenticated through your identity provider (IdP). Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP.
|
||||
With {% data variables.product.prodname_emus %}, access to your enterprise's resources on {% data variables.product.github %} must be authenticated through your identity provider (IdP). Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP.
|
||||
|
||||
After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your IdP is unavailable.
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ After you configure SAML SSO, we recommend storing your recovery codes so you ca
|
|||
|
||||
## Configure SAML SSO for {% data variables.product.prodname_emus %}
|
||||
|
||||
To configure SAML SSO for your {% data variables.enterprise.prodname_emu_enterprise %}, you must configure an application on your IdP, then configure your enterprise on {% data variables.location.product_location %}. After you configure SAML SSO, you can configure user provisioning.
|
||||
To configure SAML SSO for your {% data variables.enterprise.prodname_emu_enterprise %}, you must configure an application on your IdP, then configure your enterprise on {% data variables.product.github %}. After you configure SAML SSO, you can configure user provisioning.
|
||||
|
||||
1. [Configure your IdP](#configure-your-idp)
|
||||
1. [Configure your enterprise](#configure-your-enterprise)
|
||||
|
|
@ -64,12 +64,12 @@ To configure SAML SSO for your {% data variables.enterprise.prodname_emu_enterpr
|
|||
{%- ifversion emu-public-scim-schema %}
|
||||
* "[AUTOTITLE](/admin/identity-and-access-management/iam-configuration-reference/saml-configuration-reference)"
|
||||
{%- endif %}
|
||||
1. To test and configure your enterprise, assign yourself or the user that will configure SAML SSO for your enterprise on {% data variables.location.product_location %} to the application you configured for {% data variables.product.prodname_emus %} on your IdP.
|
||||
1. To test and configure your enterprise, assign yourself or the user that will configure SAML SSO for your enterprise on {% data variables.product.github %} to the application you configured for {% data variables.product.prodname_emus %} on your IdP.
|
||||
|
||||
> [!NOTE]
|
||||
> In order to test a successful authentication connection upon configuration, at least one user must be assigned to the IdP.
|
||||
|
||||
1. To continue configuring your enterprise on {% data variables.location.product_location %}, locate and note the following information from the application you installed on your IdP.
|
||||
1. To continue configuring your enterprise on {% data variables.product.github %}, locate and note the following information from the application you installed on your IdP.
|
||||
|
||||
| Value | Other names | Description |
|
||||
| :- | :- | :- |
|
||||
|
|
@ -79,9 +79,9 @@ To configure SAML SSO for your {% data variables.enterprise.prodname_emu_enterpr
|
|||
|
||||
### Configure your enterprise
|
||||
|
||||
After you configure SAML SSO for {% data variables.product.prodname_emus %} on your IdP, you can configure your enterprise on {% data variables.location.product_location %}.
|
||||
After you configure SAML SSO for {% data variables.product.prodname_emus %} on your IdP, you can configure your enterprise on {% data variables.product.github %}.
|
||||
|
||||
After the initial configuration of SAML SSO, the only setting you can update on {% data variables.location.product_location %} for your existing SAML configuration is the SAML certificate. If you need to update the sign-on URL or issuer URL, you must first disable SAML SSO, then reconfigure SAML SSO with the new settings. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/configuring-authentication-for-enterprise-managed-users/disabling-authentication-for-enterprise-managed-users)."
|
||||
After the initial configuration of SAML SSO, the only setting you can update on {% data variables.product.github %} for your existing SAML configuration is the SAML certificate. If you need to update the sign-on URL or issuer URL, you must first disable SAML SSO, then reconfigure SAML SSO with the new settings. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/configuring-authentication-for-enterprise-managed-users/disabling-authentication-for-enterprise-managed-users)."
|
||||
|
||||
{% data reusables.emus.sign-in-as-setup-user %}
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ redirect_from:
|
|||
|
||||
## About SAML configuration
|
||||
|
||||
To use SAML single sign-on (SSO) for authentication to {% data variables.product.product_name %}, you must configure both your external SAML identity provider (IdP) and {% ifversion ghes %}{% data variables.location.product_location %}{% elsif ghec %}your enterprise or organization on {% data variables.location.product_location %}{% endif %}. In a SAML configuration, {% data variables.product.product_name %} functions as a SAML service provider (SP). For more information about authentication for your enterprise, see "[AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/about-identity-and-access-management#authentication-methods)."
|
||||
To use SAML single sign-on (SSO) for authentication to {% data variables.product.product_name %}, you must configure both your external SAML identity provider (IdP) and {% ifversion ghes %}{% data variables.location.product_location %}{% elsif ghec %}your enterprise or organization on {% data variables.product.github %}{% endif %}. In a SAML configuration, {% data variables.product.product_name %} functions as a SAML service provider (SP). For more information about authentication for your enterprise, see "[AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/about-identity-and-access-management#authentication-methods)."
|
||||
|
||||
{% data variables.product.product_name %} provides integration according to the SAML 2.0 specification. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website.
|
||||
|
||||
|
|
@ -35,7 +35,7 @@ The SP metadata for {% data variables.product.product_name %} is available for e
|
|||
|
||||
You can configure SAML SSO for an individual organization in your enterprise. You can also configure SAML SSO for an organization if you use an individual organization on {% data variables.product.product_name %} and do not use an enterprise account. For more information, see "[AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization)."
|
||||
|
||||
The SP metadata for an organization on {% data variables.location.product_location %} is available at `https://github.com/orgs/ORGANIZATION/saml/metadata`, where **ORGANIZATION** is the name of your organization on {% data variables.location.product_location %}.
|
||||
The SP metadata for an organization on {% data variables.product.github %} is available at `https://github.com/orgs/ORGANIZATION/saml/metadata`, where **ORGANIZATION** is the name of your organization on {% data variables.product.github %}.
|
||||
|
||||
| Value | Other names | Description | Example |
|
||||
| :- | :- | :- | :- |
|
||||
|
|
@ -45,7 +45,7 @@ The SP metadata for an organization on {% data variables.location.product_locati
|
|||
|
||||
### Enterprises
|
||||
|
||||
The SP metadata for an enterprise on {% data variables.location.product_location %} is available at `https://github.com/enterprises/ENTERPRISE/saml/metadata`, where **ENTERPRISE** is the name of your enterprise on {% data variables.location.product_location %}.
|
||||
The SP metadata for an enterprise on {% data variables.product.github %} is available at `https://github.com/enterprises/ENTERPRISE/saml/metadata`, where **ENTERPRISE** is the name of your enterprise on {% data variables.product.github %}.
|
||||
|
||||
| Value | Other names | Description | Example |
|
||||
| :- | :- | :- | :- |
|
||||
|
|
@ -96,7 +96,7 @@ To specify more than one value for an attribute, use multiple `<saml2:AttributeV
|
|||
{% data variables.product.product_name %} requires that the response message from your IdP fulfill the following requirements.
|
||||
|
||||
* Your IdP must provide the `<Destination>` element on the root response document and match the ACS URL only when the root response document is signed. If your IdP signs the assertion, {% data variables.product.product_name %} will ignore the assertion.
|
||||
* Your IdP must always provide the `<Audience>` element as part of the `<AudienceRestriction>` element. The value must match your `EntityId` for {% data variables.product.product_name %}.{% ifversion ghes %} This value is the URL where you access {% data variables.location.product_location %}, such as `http(s)://HOSTNAME`.{% endif %}
|
||||
* Your IdP must always provide the `<Audience>` element as part of the `<AudienceRestriction>` element. The value must match your `EntityId` for {% data variables.product.product_name %}.{% ifversion ghes %} This value is the URL where you access {% data variables.product.github %}, such as `http(s)://HOSTNAME`.{% endif %}
|
||||
|
||||
{%- ifversion ghec %}
|
||||
* If you configure SAML for an organization, this value is `https://github.com/orgs/ORGANIZATION`.
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ redirect_from:
|
|||
permissions: Enterprise owners can download the SSO recovery codes for the enterprise account.
|
||||
---
|
||||
|
||||
In the event that your IdP is unavailable, you can use a recovery code to sign in and access your enterprise on {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable)."
|
||||
In the event that your IdP is unavailable, you can use a recovery code to sign in and access your enterprise on {% data variables.product.github %}. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable)."
|
||||
|
||||
If you did not save your recovery codes when you configured SSO, you can still access the codes from your enterprise's settings.
|
||||
|
||||
|
|
|
|||
|
|
@ -270,7 +270,7 @@ After you configure SCIM provisioning for your enterprise, you may need to migra
|
|||
|
||||
* If a request to provision a user fails with a `400` error, and the error message in your identity management system's log indicates issues with account ownership or username formatting, review "[AUTOTITLE](/admin/identity-and-access-management/iam-configuration-reference/username-considerations-for-external-authentication)."
|
||||
|
||||
* After successful authentication, {% data variables.product.product_name %} links the user who authenticated to an identity provisioned by SCIM. The unique identifiers for authentication and provisioning must match. For more information, see "[AUTOTITLE](/rest/enterprise-admin/scim#mapping-of-saml-and-scim-data)."{% ifversion ghec %} You can also view this mapping on {% data variables.location.product_location %}. See "[AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)."{% endif %}
|
||||
* After successful authentication, {% data variables.product.product_name %} links the user who authenticated to an identity provisioned by SCIM. The unique identifiers for authentication and provisioning must match. For more information, see "[AUTOTITLE](/rest/enterprise-admin/scim#mapping-of-saml-and-scim-data)."{% ifversion ghec %} You can also view this mapping on {% data variables.product.github %}. See "[AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)."{% endif %}
|
||||
|
||||
* If you manage access using groups on your identity management system, you can troubleshoot using the REST API or web UI for {% data variables.product.product_name %}.
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ If you're new to {% data variables.product.prodname_emus %} and haven't yet conf
|
|||
|
||||
## Prerequisites
|
||||
|
||||
* Your enterprise on {% data variables.location.product_location %} must currently be configured to use OIDC for authentication. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
|
||||
* Your enterprise on {% data variables.product.github %} must currently be configured to use OIDC for authentication. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
|
||||
{% data reusables.emus.migration-roles-prereq %}
|
||||
{% data reusables.emus.migration-schedule-downtime %}
|
||||
|
||||
|
|
|
|||
|
|
@ -33,17 +33,17 @@ If you're new to {% data variables.product.prodname_emus %} and haven't yet conf
|
|||
|
||||
## Prerequisites
|
||||
|
||||
* Your enterprise on {% data variables.location.product_location %} must currently be configured to use SAML for authentication, with Entra ID as your identity provider (IdP). For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)."
|
||||
* Your enterprise on {% data variables.product.github %} must currently be configured to use SAML for authentication, with Entra ID as your identity provider (IdP). For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)."
|
||||
{% data reusables.emus.migration-roles-prereq %}
|
||||
{% data reusables.emus.migration-schedule-downtime %}
|
||||
|
||||
## Migrating your enterprise
|
||||
|
||||
To migrate your enterprise from SAML to OIDC, you will disable your existing {% data variables.product.prodname_emu_idp_application %} application on Entra ID, prepare and begin the migration as the setup user for your enterprise on {% data variables.location.product_location %}, then install and configure the new application for OIDC on Entra ID. After the migration is complete and Entra ID provisions your users, the users can authenticate to access your enterprise's resources on {% data variables.location.product_location %} using OIDC.
|
||||
To migrate your enterprise from SAML to OIDC, you will disable your existing {% data variables.product.prodname_emu_idp_application %} application on Entra ID, prepare and begin the migration as the setup user for your enterprise on {% data variables.product.github %}, then install and configure the new application for OIDC on Entra ID. After the migration is complete and Entra ID provisions your users, the users can authenticate to access your enterprise's resources on {% data variables.product.github %} using OIDC.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Migration of your enterprise from SAML to OIDC can take up to an hour. During the migration, users cannot access your enterprise on {% data variables.location.product_location %}.
|
||||
**Warning**: Migration of your enterprise from SAML to OIDC can take up to an hour. During the migration, users cannot access your enterprise on {% data variables.product.github %}.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
|
|
@ -57,7 +57,7 @@ To migrate your enterprise from SAML to OIDC, you will disable your existing {%
|
|||
1. At the bottom of the page, next to "Migrate to OpenID Connect single sign-on", click **Configure with Azure**.
|
||||
1. Read the warning, then click **I understand, begin migrating to OpenID Connect**.
|
||||
{% data reusables.enterprise-accounts.emu-azure-admin-consent %}
|
||||
1. After you grant consent, a new browser window will open to {% data variables.location.product_location %} and display a new set of recovery codes for your {% data variables.enterprise.prodname_emu_enterprise %}. Download the codes, then click **Enable OIDC authentication**.
|
||||
1. After you grant consent, a new browser window will open to {% data variables.product.github %} and display a new set of recovery codes for your {% data variables.enterprise.prodname_emu_enterprise %}. Download the codes, then click **Enable OIDC authentication**.
|
||||
1. Wait for the migration to complete, which can take up to an hour. To check the status of the migration, navigate to your enterprise's authentication security settings page. If "Require SAML authentication" is selected, the migration is still in progress.
|
||||
|
||||
{% warning %}
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ You can choose between configuring SAML at the enterprise level, which applies t
|
|||
|
||||
### Authentication with {% data variables.product.prodname_emus %} and federation
|
||||
|
||||
If you need more control of the accounts for your enterprise members on {% data variables.location.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.location.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)."
|
||||
If you need more control of the accounts for your enterprise members on {% data variables.product.github %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.product.github %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)."
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ redirect_from:
|
|||
|
||||
If you decide to use SAML instead of {% data variables.product.prodname_emus %}, you must choose whether to configure SAML at the enterprise level or the organization level.
|
||||
|
||||
If some groups within your enterprise must use different SAML authentication providers to grant access to your resources on {% data variables.location.product_location %}, configure SAML for individual organizations. You can implement SAML for your organizations over time by allowing users to gradually authenticate using SAML, or you can require SAML authentication by a certain date. Organization members who do not authenticate using SAML by this date will be removed. For more information about organization-level SAML, see "[AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)."
|
||||
If some groups within your enterprise must use different SAML authentication providers to grant access to your resources on {% data variables.product.github %}, configure SAML for individual organizations. You can implement SAML for your organizations over time by allowing users to gradually authenticate using SAML, or you can require SAML authentication by a certain date. Organization members who do not authenticate using SAML by this date will be removed. For more information about organization-level SAML, see "[AUTOTITLE](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)."
|
||||
|
||||
If you configure SAML at the organization level, members are not required to authenticate via SAML to access internal repositories. For more information about internal repositories, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)."
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Troubleshooting SAML authentication
|
||||
shortTitle: Troubleshoot SAML SSO
|
||||
intro: 'If you use SAML single sign-on (SSO) and people are unable to authenticate to access {% data variables.location.product_location %}, you can troubleshoot the problem.'
|
||||
intro: 'If you use SAML single sign-on (SSO) and people are unable to authenticate to access {% data variables.product.github %}, you can troubleshoot the problem.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ topics:
|
|||
|
||||
You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. For more information, see "[AUTOTITLE](/webhooks-and-events/webhooks)."
|
||||
|
||||
For example, you can configure {% data variables.location.product_location %} to send a webhook when someone creates, deletes, or modifies a repository or organization within your enterprise. You can configure the server to automatically perform a task after receiving the webhook.
|
||||
For example, you can configure {% data variables.product.github %} to send a webhook when someone creates, deletes, or modifies a repository or organization within your enterprise. You can configure the server to automatically perform a task after receiving the webhook.
|
||||
|
||||
{% data reusables.enterprise_user_management.manage-global-webhooks-api %}
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ You are responsible for meeting any legal obligations that accompany the viewing
|
|||
|
||||
If you choose to display IP addresses for your enterprise account, the IP addresses will appear in both your enterprise's audit log and the audit log of every organization owned by your enterprise. Alternatively, you can enable the display of IP addresses in the audit log for individual organizations. For more information, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/displaying-ip-addresses-in-the-audit-log-for-your-organization)."
|
||||
|
||||
You can display IP addresses in the audit log regardless of which authentication method you use for your enterprise on {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
|
||||
You can display IP addresses in the audit log regardless of which authentication method you use for your enterprise on {% data variables.product.github %}. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
|
||||
|
||||
{% data reusables.audit_log.users-agree-to-ip-collection %}
|
||||
|
||||
|
|
|
|||
|
|
@ -286,7 +286,7 @@ To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint, make sure
|
|||
|
||||
## Pausing audit log streaming
|
||||
|
||||
Pause the stream to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.location.product_location %} and are then exported when you unpause the stream.
|
||||
Pause the stream to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.github %} and are then exported when you unpause the stream.
|
||||
|
||||
{% ifversion streaming-datadog %}
|
||||
Datadog only accepts logs from up to 18 hours in the past. If you pause a stream to a Datadog endpoint for more than 18 hours, you risk losing logs that Datadog won't accept after you resume streaming.
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@ Before you can add your local repository to {% data variables.product.prodname_d
|
|||
|
||||
{% data reusables.migrations.create-empty-repo %}
|
||||
|
||||
1. At the top of your repository on {% data variables.location.product_location %}'s Quick Setup page, click {% octicon "copy" aria-label="Copy to clipboard" %} to copy the remote repository URL.
|
||||
1. At the top of your repository on {% data variables.product.github %}'s Quick Setup page, click {% octicon "copy" aria-label="Copy to clipboard" %} to copy the remote repository URL.
|
||||
|
||||
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ Before you can add your local repository to {% data variables.product.prodname_d
|
|||
git remote -v
|
||||
```
|
||||
|
||||
1. To push the changes in your local repository to {% data variables.location.product_location %}, run the following command.
|
||||
1. To push the changes in your local repository to {% data variables.product.github %}, run the following command.
|
||||
|
||||
```shell
|
||||
git push -u origin main
|
||||
|
|
@ -131,7 +131,7 @@ Before you can add your local repository to {% data variables.product.prodname_d
|
|||
|
||||
{% data reusables.migrations.create-empty-repo %}
|
||||
|
||||
1. At the top of your repository on {% data variables.location.product_location %}'s Quick Setup page, click {% octicon "copy" aria-label="Copy to clipboard" %} to copy the remote repository URL.
|
||||
1. At the top of your repository on {% data variables.product.github %}'s Quick Setup page, click {% octicon "copy" aria-label="Copy to clipboard" %} to copy the remote repository URL.
|
||||
|
||||
|
||||
|
||||
|
|
@ -150,7 +150,7 @@ Before you can add your local repository to {% data variables.product.prodname_d
|
|||
git remote -v
|
||||
```
|
||||
|
||||
1. To push the changes in your local repository to {% data variables.location.product_location %}, run the following command.
|
||||
1. To push the changes in your local repository to {% data variables.product.github %}, run the following command.
|
||||
|
||||
```shell
|
||||
git push origin main
|
||||
|
|
@ -164,7 +164,7 @@ Before you can add your local repository to {% data variables.product.prodname_d
|
|||
|
||||
{% data reusables.migrations.create-empty-repo %}
|
||||
|
||||
1. At the top of your repository on {% data variables.location.product_location %}'s Quick Setup page, click {% octicon "copy" aria-label="Copy to clipboard" %} to copy the remote repository URL.
|
||||
1. At the top of your repository on {% data variables.product.github %}'s Quick Setup page, click {% octicon "copy" aria-label="Copy to clipboard" %} to copy the remote repository URL.
|
||||
|
||||
|
||||
|
||||
|
|
@ -183,7 +183,7 @@ Before you can add your local repository to {% data variables.product.prodname_d
|
|||
git remote -v
|
||||
```
|
||||
|
||||
1. To push the changes in your local repository to {% data variables.location.product_location %}, run the following command.
|
||||
1. To push the changes in your local repository to {% data variables.product.github %}, run the following command.
|
||||
|
||||
```shell
|
||||
git push origin main
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
When anyone creates an account on {% data variables.location.product_location %}, the person agrees to {% data variables.product.company_short %}'s collection of basic information about connections to {% data variables.product.company_short %}'s services, including source IP address. For more information, see "[AUTOTITLE](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#usage-information)."
|
||||
When anyone creates an account on {% data variables.product.github %}, the person agrees to {% data variables.product.company_short %}'s collection of basic information about connections to {% data variables.product.company_short %}'s services, including source IP address. For more information, see "[AUTOTITLE](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#usage-information)."
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
* You'll need to access both your enterprise on {% data variables.location.product_location %} and your tenant on Entra ID.
|
||||
* You'll need to access both your enterprise on {% data variables.product.github %} and your tenant on Entra ID.
|
||||
|
||||
* To configure the {% data variables.product.prodname_emu_idp_oidc_application %} application on Entra ID, you must sign into the Entra ID tenant as a user with the Global Administrator role.
|
||||
* To sign in as the setup user for your enterprise on {% data variables.location.product_location %}, you must use a recovery code for the enterprise. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes)."
|
||||
* To sign in as the setup user for your enterprise on {% data variables.product.github %}, you must use a recovery code for the enterprise. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes)."
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. To ensure you can still access your enterprise on {% data variables.location.product_location %} if your IdP is unavailable in the future, click **Download**, **Print**, or **Copy** to save your recovery codes. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes)."
|
||||
1. To ensure you can still access your enterprise on {% data variables.product.github %} if your IdP is unavailable in the future, click **Download**, **Print**, or **Copy** to save your recovery codes. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes)."
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
To create, manage, and deactivate user accounts for your enterprise members on {% data variables.location.product_location %}, your IdP {% ifversion ghec %}must{% else %}can{% endif %} implement SCIM for communication with {% data variables.product.prodname_dotcom %}. SCIM is an open specification for management of user identities between systems. Different IdPs provide different experiences for the configuration of SCIM provisioning.
|
||||
To create, manage, and deactivate user accounts for your enterprise members on {% data variables.product.github %}, your IdP {% ifversion ghec %}must{% else %}can{% endif %} implement SCIM for communication with {% data variables.product.prodname_dotcom %}. SCIM is an open specification for management of user identities between systems. Different IdPs provide different experiences for the configuration of SCIM provisioning.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
{% data variables.product.product_name %} normalizes a value from your {% ifversion ghec %}IdP{% elsif ghes %}external authentication provider{% endif %} to determine the username for each new personal account {% ifversion ghec %}in your enterprise on {% data variables.location.product_location %}{% elsif ghes %}on {% data variables.location.product_location %}{% endif %}.
|
||||
{% data variables.product.product_name %} normalizes a value from your {% ifversion ghec %}IdP{% elsif ghes %}external authentication provider{% endif %} to determine the username for each new personal account {% ifversion ghec %}in your enterprise on {% data variables.product.github %}{% elsif ghes %}on {% data variables.location.product_location %}{% endif %}.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
With SCIM, you manage the lifecycle of user accounts from your IdP:
|
||||
|
||||
* {% ifversion ghec %}After you configure provisioning for {% data variables.product.prodname_emus %}, your IdP uses SCIM to provision user accounts on {% data variables.location.product_location %} and add the accounts to your enterprise.{% else %}When you provision a new user, your IdP will prompt {% data variables.location.product_location %} to create an account and send an onboarding email to the user.{% endif %} If you assign a group to the application in your IdP, your IdP will provision accounts for all members of the group.
|
||||
* {% ifversion ghec %}After you configure provisioning for {% data variables.product.prodname_emus %}, your IdP uses SCIM to provision user accounts on {% data variables.product.github %} and add the accounts to your enterprise.{% else %}When you provision a new user, your IdP will prompt {% data variables.location.product_location %} to create an account and send an onboarding email to the user.{% endif %} If you assign a group to the application in your IdP, your IdP will provision accounts for all members of the group.
|
||||
* When you update information associated with a user's identity on your IdP, your IdP will update the user's account on {% data variables.product.prodname_dotcom %}.
|
||||
* When you unassign the user from the IdP application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username{% ifversion ghec %} with the short code appended{% endif %}.
|
||||
* If you reassign a user to the IdP application or reactivate their account on your IdP, the user account will be reactivated, and the username will be restored.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
1. Create a new repository on {% data variables.location.product_location %}. To avoid errors, do not initialize the new repository with README, license, or gitignore files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-new-repository)."
|
||||
1. Create a new repository on {% data variables.product.github %}. To avoid errors, do not initialize the new repository with README, license, or gitignore files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/creating-a-new-repository)."
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
You can view the single sign-on identity that a member has linked to their account on {% data variables.location.product_location %}.
|
||||
You can view the single sign-on identity that a member has linked to their account on {% data variables.product.github %}.
|
||||
|
||||
If a member links the wrong identity to their account on {% data variables.location.product_location %}, you can revoke the linked identity to allow the member to try again.
|
||||
If a member links the wrong identity to their account on {% data variables.product.github %}, you can revoke the linked identity to allow the member to try again.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
If you don't see **Configure SSO**, ensure that you have authenticated at least once through your SAML IdP to access resources on {% data variables.location.product_location %}. For more information, see "[AUTOTITLE](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)."
|
||||
If you don't see **Configure SSO**, ensure that you have authenticated at least once through your SAML IdP to access resources on {% data variables.product.github %}. For more information, see "[AUTOTITLE](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)."
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
{% data variables.product.company_short %} recommends that you test provisioning in an environment that's isolated from the production data on your IdP and {% data variables.location.product_location %}.
|
||||
{% data variables.product.company_short %} recommends that you test provisioning in an environment that's isolated from the production data on your IdP and {% data variables.product.github %}.
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
{% data variables.product.company_short %} recommends that you test provisioning in an environment that's isolated from the production data on your IdP and {% data variables.location.product_location %}.
|
||||
{% data variables.product.company_short %} recommends that you test provisioning in an environment that's isolated from the production data on your IdP and {% data variables.product.github %}.
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче