зеркало из https://github.com/github/docs.git
New translation batch for es (#29963)
* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/fix-translation-errors.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=es * run script/i18n/reset-known-broken-translation-files.js
This commit is contained in:
docubot
GitHub
Родитель
74db5c9eca
Коммит
b425ae03a6
|
|
@ -99,7 +99,7 @@ Los secretos que se almacenan en un ambiente sólo se encuentran disponibles par
|
|||
1. Ingresa el valor del secreto.
|
||||
1. Haz clic en **Agregar secreto** (Agregar secreto).
|
||||
|
||||
También puedes crear y configurar ambientes a través de la API de REST. Para obtener más información, consulta las secciones "[Ambientes](/rest/reference/repos#environments)" y "[Secretos](/rest/reference/actions#secrets)".
|
||||
También puedes crear y configurar ambientes a través de la API de REST. For more information, see "[Deployment environments](/rest/deployments/environments)," "[GitHub Actions Secrets](/rest/actions/secrets)," and "[Deployment branch policies](/rest/deployments/branch-policies)."
|
||||
|
||||
El ejecutar un flujo de trabajo que referencie un ambiente que no existe creará un ambiente con el nombre referenciado. El ambiente recién creado no tendrá configurada ninguna regla de protección o secreto. Cualquiera que pueda editar flujos de trabajo en el repositorio podrá crear ambientes a través de un archivo de flujo de trabajo, pero solo los administradoresd e repositorio pueden configurar el ambiente.
|
||||
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ runs-on: [self-hosted, linux, x64, gpu]
|
|||
- `x64` - Utiliza únicamente un ejecutor basado en hardware x64.
|
||||
- `gpu` - Esta etiqueta personalizada se asignó manualmente a los ejecutores auto-hospedados con hardware de GPU instalado.
|
||||
|
||||
Estas etiquetas operan acumulativamente, así que las etiquetas de un ejecutor auto-hospedado deberán empatar con los cuatro criterios para poder ser elegibles para procesar el job.
|
||||
These labels operate cumulatively, so a self-hosted runner must have all four labels to be eligible to process the job.
|
||||
|
||||
## Precedencia de enrutamiento para los ejecutores auto-hospedados
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ versions:
|
|||
|
||||
Las acciones pueden comunicarse con la máquina del ejecutor para establecer variables de entorno, valores de salida utilizados por otras acciones, agregar mensajes de depuración a los registros de salida y otras tareas.
|
||||
|
||||
La mayoría de los comandos de los flujos de trabajo utilizan el comando `echo` en un formato específico, mientras que otras se invocan si escribes a un archivo. For more information, see "[Environment files](#environment-files)."
|
||||
La mayoría de los comandos de los flujos de trabajo utilizan el comando `echo` en un formato específico, mientras que otras se invocan si escribes a un archivo. Para obtener más información, consulta la sección "[Archivos de ambiente](#environment-files)".
|
||||
|
||||
### Ejemplo
|
||||
|
||||
|
|
|
|||
|
|
@ -18,14 +18,15 @@ shortTitle: Create enterprise account
|
|||
|
||||
{% data reusables.enterprise.create-an-enterprise-account %} If you pay by invoice, you can create an enterprise account yourself on {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you.
|
||||
|
||||
An enterprise account is included in {% data variables.product.prodname_ghe_cloud %}, so creating one will not affect your bill.
|
||||
An enterprise account is included with {% data variables.product.prodname_ghe_cloud %}. Creation of an enterprise account does not result in additional charges on your bill.
|
||||
|
||||
When you create an enterprise account, your existing organization will automatically be owned by the enterprise account. All current owners of your organization will become owners of the enterprise account. All current billing managers of the organization will become billing managers of the new enterprise account. The current billing details of the organization, including the organization's billing email address, will become billing details of the new enterprise account.
|
||||
When you create an enterprise account that owns your existing organization on {% data variables.product.product_name %}, the organization's resources remain accessible to members at the same URLs. After you add your organization to the enterprise account, the following changes will apply to the organization.
|
||||
|
||||
If the organization is connected to {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %} via {% data variables.product.prodname_github_connect %}, upgrading the organization to an enterprise account **will not** update the connection. If you want to connect to the new enterprise account, you must disable and re-enable {% data variables.product.prodname_github_connect %}.
|
||||
- Your existing organization will automatically be owned by the enterprise account.
|
||||
- {% data variables.product.company_short %} bills the enterprise account for usage within all organizations owned by the enterprise. The current billing details for the organization, including the organization's billing email address, will become billing details for the new enterprise account. For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
|
||||
- All current owners of your organization will become owners of the enterprise account, and all current billing managers of the organization will become billing managers of the new enterprise account. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
|
||||
|
||||
- "[Managing {% data variables.product.prodname_github_connect %}](/enterprise-server@latest/admin/configuration/configuring-github-connect/managing-github-connect)" in the {% data variables.product.prodname_ghe_server %} documentation
|
||||
- "[Managing {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/managing-github-connect)" in the {% data variables.product.prodname_ghe_managed %} documentation
|
||||
For more information about the changes that apply to an organization after you add the organization to an enterprise, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#about-addition-of-organizations-to-your-enterprise-account)."
|
||||
|
||||
## Creating an enterprise account on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
|
|
|
|||
|
|
@ -17,13 +17,26 @@ shortTitle: Add organizations
|
|||
permissions: Enterprise owners can add organizations to an enterprise.
|
||||
---
|
||||
|
||||
## About organizations
|
||||
## About addition of organizations to your enterprise account
|
||||
|
||||
Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
|
||||
|
||||
You can add a new or existing organization to your enterprise in your enterprise account's settings.
|
||||
You can add new organizations to your enterprise account. If you do not use {% data variables.product.prodname_emus %}, you can add existing organizations on {% data variables.product.product_location %} to your enterprise. You cannot add an existing organization from an {% data variables.product.prodname_emu_enterprise %} to a different enterprise.
|
||||
|
||||
You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
|
||||
{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
|
||||
|
||||
After you add an existing organization to your enterprise, the organization's resources remain accessible to members at the same URLs, and the following changes will apply.
|
||||
|
||||
- The organization's members will become members of the enterprise, and {% data variables.product.company_short %} will bill the enterprise account for the organization's usage. You must ensure that the enterprise account has enough licenses to accommodate any new members. For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
|
||||
- Enterprise owners can manage their role within the organization. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."
|
||||
- Any policies applied to the enterprise will apply to the organization. For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)."
|
||||
- If SAML SSO is configured for the enterprise account, the enterprise's SAML configuration will apply to the organization. If the organization used SAML SSO, the enterprise account's configuration will replace the organization's configuration. SCIM is not available for enterprise accounts, so SCIM will be disabled for the organization. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)" and "[Switching your SAML configuration from an organization to an enterprise account](/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
|
||||
- If SAML SSO was configured for the organization, members' existing personal access tokens (PATs) or SSH keys that were authorized to access the organization's resources will be authorized to access the same resources. To access additional organizations owned by the enterprise, members must authorize the PAT or key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
|
||||
- If the organization was connected to {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %} using {% data variables.product.prodname_github_connect %}, adding the organization to an enterprise will not update the connection. {% data variables.product.prodname_github_connect %} features will no longer function for the organization. To continue using {% data variables.product.prodname_github_connect %}, you must disable and re-enable the feature. For more information, see the following articles.
|
||||
|
||||
- "[Managing {% data variables.product.prodname_github_connect %}](/enterprise-server@latest/admin/configuration/configuring-github-connect/managing-github-connect)" in the {% data variables.product.prodname_ghe_server %} documentation
|
||||
- "[Managing {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/managing-github-connect)" in the {% data variables.product.prodname_ghe_managed %} documentation
|
||||
- If the organization used billed {% data variables.product.prodname_marketplace %} apps, the organization can continue to use the apps, but must pay the vendor directly. For more information, contact the app's vendor.
|
||||
|
||||
## Creating an organization in your enterprise account
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Acerca de la autenticación con el inicio de sesión único de SAML
|
||||
intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).'
|
||||
intro: 'Puedes acceder a {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %} una organización que utilice el inicio de sesión único (SSO) de SAML{% endif %} si te autenticas {% ifversion ghae %}con el inicio de sesión único (SSO) de SAML {% endif %}mediante un proveedor de identidad (IdP).'
|
||||
redirect_from:
|
||||
- /articles/about-authentication-with-saml-single-sign-on
|
||||
- /github/authenticating-to-github/about-authentication-with-saml-single-sign-on
|
||||
|
|
@ -29,9 +29,9 @@ Si nopuedes acceder a {% data variables.product.product_name %}, contacta al pro
|
|||
|
||||
{% data reusables.saml.dotcom-saml-explanation %} Los propietarios de las organizaciones pueden invitar a tu cuenta personal de {% data variables.product.prodname_dotcom %} para que se una a sus organizaciones que utilicen el SSO de SAML, lo cual te permitirá contribuir con la organización y retener tu identidad existente y las contribuciones en {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %}
|
||||
Si eres miembro de una {% data variables.product.prodname_emu_enterprise %}, necesitarás utilizar una cuenta nueva en su lugar, la cual se aprovisione para ti y la controle tu empresa. {% data reusables.enterprise-accounts.emu-more-info-account %}
|
||||
|
||||
When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. Después de que te autentiques exitosamente con tu cuenta en el IdP, este te redirigirá de vuelta a {% data variables.product.prodname_dotcom %}, en donde podrás acceder a los recursos de la organización.
|
||||
Cuando accedes a los recursos privados dentro de una organización que utiliza el SSO de SAML, {% data variables.product.prodname_dotcom %} te redireccionará al IdP de SAML de la organización para que te autentiques. Después de que te autentiques exitosamente con tu cuenta en el IdP, este te redirigirá de vuelta a {% data variables.product.prodname_dotcom %}, en donde podrás acceder a los recursos de la organización.
|
||||
|
||||
{% data reusables.saml.outside-collaborators-exemption %}
|
||||
|
||||
|
|
@ -39,15 +39,15 @@ Si te has autenticado recientemente con tu SAML IdP de la organización en tu na
|
|||
|
||||
{% data reusables.saml.you-must-periodically-authenticate %}
|
||||
|
||||
## Linked SAML identities
|
||||
## Identidades de SAML enlazadas
|
||||
|
||||
When you authenticate with your IdP account and return to {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_dotcom %} will record a link in the organization or enterprise between your {% data variables.product.prodname_dotcom %} personal account and the SAML identity you signed into. This linked identity is used to validate your membership in that organization, and depending on your organization or enterprise setup, is also used to determine which organizations and teams you're a member of as well. Each {% data variables.product.prodname_dotcom %} account can be linked to exactly one SAML identity per organization. Likewise, each SAML identity can be linked to exactly one {% data variables.product.prodname_dotcom %} account in an organization.
|
||||
Cuando te autenticas con tu cuetna de IdP y regresas a {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_dotcom %} registrará un enlace en la organización o empresa entre tu cuenta personal de {% data variables.product.prodname_dotcom %} y la identidad de SAML en la cual iniciaste sesión. Esta identidad enlazada se utiliza para validar tu membrecía en dicha organización y, dependiendo de tu configuración de empresa u organización, también se utiliza para determinar de qué equipos y organizaciones eres miembro. Cada cuenta de {% data variables.product.prodname_dotcom %} puede enlazarse a exactamente una identidad de SAML por organización. Del mismo modo, cada identidad de SAML puede vincularse a exactamente una cuenta de {% data variables.product.prodname_dotcom %} en una organización.
|
||||
|
||||
If you sign in with a SAML identity that is already linked to another {% data variables.product.prodname_dotcom %} account, you will receive an error message indicating that you cannot sign in with that SAML identity. This situation can occur if you are attempting to use a new {% data variables.product.prodname_dotcom %} account to work inside of your organization. If you didn't intend to use that SAML identity with that {% data variables.product.prodname_dotcom %} account, then you'll need to sign out of that SAML identity and then repeat the SAML login. If you do want to use that SAML identity with your {% data variables.product.prodname_dotcom %} account, you'll need to ask your admin to unlink your SAML identity from your old account, so that you can link it to your new account. Depending on the setup of your organization or enterprise, your admin may also need to reassign your identity within your SAML provider. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)".
|
||||
Si inicias sesión con una identidad de SAML que ya esté vinculada a otra cuenta de {% data variables.product.prodname_dotcom %}, recibirás un mensaje de error que indicará que no puedes iniciar sesión con esa identidad de SAML. Esta situación puede ocurrir si estás intentando utilizar una cuenta nueva de {% data variables.product.prodname_dotcom %} para trabajar dentro de tu organización. Si no pretendes utilizar esa identidad de SAML con esa cuenta de {% data variables.product.prodname_dotcom %}, entonces necesitarás salir de sesión en esa identidad de SAML y luego repetir el inicio de sesión de SAML. Si no quieres utilizar esa identidad de SAML con tu cuenta de {% data variables.product.prodname_dotcom %}, necesitarás pedirle a tu administrador que desvincule tu identidad de SAML de tu cuenta anterior, para que puedas vincularla a tu cuenta nueva. Dependiendo de la configuración de tu organización o empresa, tu administrador también podría necesitar volver a asignar tu identidad dentro de tu proveedor de SAML. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)".
|
||||
|
||||
If the SAML identity you sign in with does not match the SAML identity that is currently linked to your {% data variables.product.prodname_dotcom %} account, you'll receive a warning that you are about to relink your account. Because your SAML identity is used to govern access and team membership, continuing with the new SAML identity can cause you to lose access to teams and organizations inside of {% data variables.product.prodname_dotcom %}. Only continue if you know that you're supposed to use that new SAML identity for authentication in the future.
|
||||
Si la identidad de SAML con la que iniciaste sesión no coincide con la identidad de SAML que está vinculada actualmente a tu cuenta de {% data variables.product.prodname_dotcom %}, recibirás una advertencia de que estás por volver a vincular tu cuenta. Ya que tu identidad de SAML se utiliza para regir el acceso y la membrecía de equipo, el seguir con la nueva identidad de SAML puede ocasionar que pierdas acceso a los equipos y organizaciones dentro de {% data variables.product.prodname_dotcom %}. Procede solo si sabes que debes utilizar la nueva identidad de SAML para la autenticación en el futuro.
|
||||
|
||||
## Authorizing PATs and SSH keys with SAML SSO
|
||||
## Autorizar llaves SSH y PAT con el SSO de SAML
|
||||
|
||||
Para usar la API o Git en la línea de comandos para acceder a contenido protegido en una organización que usa SAML SSO, necesitarás usar un token de acceso personal autorizado a través de HTTPS o una clave SSH autorizada.
|
||||
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@ Las {% data variables.product.prodname_oauth_apps %} pueden solicitar diferentes
|
|||
| Datos personales del usuario | Entre los datos del usuario se incluye información que se encuentra en tu perfil de usuario, como tu nombre, dirección de correo electrónico y ubicación. |
|
||||
| Repositorios | La información del repositorio incluye los nombres de los colaboradores, las ramas que creaste y los archivos actuales dentro de tu repositorio. Las apps pueden solicitar acceso a repositorios públicos o privados a nivel del usuario. |
|
||||
| Eliminación de repositorio | Las apps pueden solicitar la eliminación de los repositorios que administras,, pero no tendrán acceso a tu código. |{% ifversion projects-oauth-scope %}
|
||||
| Proyectos | Access to user and organization {% data variables.projects.projects_v2 %}. Las apps pueden solicitar ya sea un acceso de lectura/escritura o de solo lectura.
|
||||
| Proyectos | Acceso a los {% data variables.projects.projects_v2 %} de usuarios y organizaciones. Las apps pueden solicitar ya sea un acceso de lectura/escritura o de solo lectura.
|
||||
{% endif %}
|
||||
|
||||
## Solicitar permisos actualizados
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Modo sudo
|
||||
intro: 'To confirm access to your account before you perform a potentially sensitive action, {% data variables.product.product_location %} prompts for authentication.'
|
||||
intro: 'Para confirmar el acceso a tu cuenta antes de que realices una acción potencialmente sensible, {% data variables.product.product_location %} pide una autenticación.'
|
||||
redirect_from:
|
||||
- /articles/sudo-mode
|
||||
- /github/authenticating-to-github/sudo-mode
|
||||
|
|
@ -15,38 +15,38 @@ topics:
|
|||
- Access management
|
||||
---
|
||||
|
||||
## About sudo mode
|
||||
## Acerca del modo sudo
|
||||
|
||||
To maintain the security of your account when you perform a potentially sensitive action on {% data variables.product.product_location %}, you must authenticate even though you're already signed in. For example, {% data variables.product.company_short %} considers the following actions sensitive because each action could allow a new person or system to access your account.
|
||||
Para mantener la seguridad de tu cuenta cuando realizas una acción potencialmente sensible en {% data variables.product.product_location %}, debes autenticarte aunque ya hayas iniciado sesión. Por ejemplo, {% data variables.product.company_short %} considera las siguientes acciones como sensibles, ya que cada acción podría permitir que una persona o sistema nuevos accedan a tu cuenta.
|
||||
|
||||
- Modification of an associated email address
|
||||
- Authorization of a third-party application
|
||||
- Addition of a new SSH key
|
||||
- Modificación de una dirección de correo electrónico asociada
|
||||
- Autorización de una aplicación de terceros
|
||||
- Adición de una llave SSH nueva
|
||||
|
||||
After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. {% data variables.product.product_name %} will wait a few hours before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer.
|
||||
Después de que te autenticas para realizar una acción sensible, tu sesión se queda temporalmente en "modo sudo". En el modo sudo, puedes realizar acciones sensibles sin autenticación. {% data variables.product.product_name %} esperará algunas horas antes de pedirte una autenticación nuevamente. Durante este tiempo, cualquier acción sensible que lleves a cabo restablecerá el cronómetro.
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: If {% data variables.product.product_location %} uses an external authentication method like CAS or SAML SSO, you will not receive prompts to enter sudo mode. Para obtener más información, contacta a tu administrador de sitio.
|
||||
**Nota**: Si {% data variables.product.product_location %} utiliza un método de autenticación externa como CAS o el SSO de SAML, no recibirás mensajes para ingresar en modo sudo. Para obtener más información, contacta a tu administrador de sitio.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
"sudo" is a reference to a program on Unix systems, where the name is short for "**su**peruser **do**." For more information, see [sudo](https://wikipedia.org/wiki/Sudo) on Wikipedia.
|
||||
"sudo" es una referencia a un programa en los sistemas Unix, en donde es un apócope para "**su**peruser **do**". Para obtener más información, consulta el término [sudo](https://wikipedia.org/wiki/Sudo) en Wikipedia.
|
||||
|
||||
## Confirming access for sudo mode
|
||||
## Confirmar el acceso para el modo sudo
|
||||
|
||||
To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge %}can{% else %}must{% endif %} authenticate with your password.{% ifversion totp-and-mobile-sudo-challenge %} Optionally, you can use a different authentication method, like {% ifversion fpt or ghec %}a security key, {% data variables.product.prodname_mobile %}, or a 2FA code{% elsif ghes %}a security key or a 2FA code{% endif %}.{% endif %}
|
||||
Para confirmar el acceso al modo sudo, {% ifversion totp-and-mobile-sudo-challenge %}puedes{% else %}debes{% endif %} autenticarte con tu contraseña.{% ifversion totp-and-mobile-sudo-challenge %} Opcionalmente, puedes utilizar un método de autenticación diferente, como {% ifversion fpt or ghec %}una llave de seguridad, {% data variables.product.prodname_mobile %}o un código de 2FA{% elsif ghes %}una llave de seguridad o un código de 2FA{% endif %}.{% endif %}
|
||||
|
||||
{%- ifversion totp-and-mobile-sudo-challenge %}
|
||||
- [Confirming access using a security key](#confirming-access-using-a-security-key)
|
||||
- [Confirmar el acceso utilizando una llave de seguridad](#confirming-access-using-a-security-key)
|
||||
{%- ifversion fpt or ghec %}
|
||||
- [Confirming access using GitHub Mobile](#confirming-access-using-github-mobile)
|
||||
- [Confirmar el acceso utilizando GitHub Mobile](#confirming-access-using-github-mobile)
|
||||
{%- endif %}
|
||||
- [Confirming access using a 2FA code](#confirming-access-using-a-2fa-code)
|
||||
- [Confirmar el acceso utilizando un código de 2FA](#confirming-access-using-a-2fa-code)
|
||||
- [Confirmar el acceso utilizando tu contraseña](#confirming-access-using-your-password)
|
||||
{%- endif %}
|
||||
|
||||
|
|
@ -54,9 +54,9 @@ To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge
|
|||
|
||||
### Confirmar el acceso utilizando una llave de seguridad
|
||||
|
||||
You must configure two-factor authentication (2FA) for your account using a security key to confirm access to your account for sudo mode using the security key. Para obtener más información, consulta "[Configurar autenticación de dos factores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)".
|
||||
Debes configurar la autenticación bifactorial (2FA) para tu cuenta utilizando una llave de seguridad para confirmar el acceso a tu cuenta para el modo sudo utilizando la llave de seguridad. Para obtener más información, consulta "[Configurar autenticación de dos factores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)".
|
||||
|
||||
When prompted to authenticate for sudo mode, click **Use security key**, then follow the prompts.
|
||||
Cuando se te pide autenticarte para el modo sudo, haz clic en **Utilizar llave de seguridad** y luego sigue las instrucciones de los mensajes.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -45,7 +45,11 @@ Puedes ver tu uso actual en tu [Portal de cuenta de Azure](https://portal.azure.
|
|||
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% data variables.product.company_short %} factura mensualmente por la cantidad total de plazas con licencia para tu organización o cuenta empresarial, así como por cualquier servicio adicional que utilices con {% data variables.product.prodname_ghe_cloud %}, tal como los minutos de {% data variables.product.prodname_actions %}. Para obtener más información sobre la porción de asientos con licencia de tu factura, consulta la sección "[Acerca de los precios por usuario](/billing/managing-billing-for-your-github-account/about-per-user-pricing)".
|
||||
When you use an enterprise account on {% data variables.product.product_location %}, the enterprise account is the central point for all billing within your enterprise, including the organizations that your enterprise owns.
|
||||
|
||||
If you use {% data variables.product.product_name %} with an individual organization and do not yet have an enterprise account, you create an enterprise account and add your organization. Para obtener más información, consulta la sección "[Crear una cuenta empresarial](/admin/overview/creating-an-enterprise-account)".
|
||||
|
||||
{% data variables.product.company_short %} bills monthly for the total number of licensed seats for your enterprise account, as well as any additional services you use with {% data variables.product.prodname_ghe_cloud %}, such as {% data variables.product.prodname_actions %} minutes. If you use a standalone organization on {% data variables.product.product_name %}, you'll be billed at the organization level for all usage. For more information your bill's license seats, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)."
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
|
|
|
|||
|
|
@ -22,6 +22,8 @@ Para garantizar que ves los detalles actualizados de la licencia en {% data vari
|
|||
|
||||
Si no quieres habilitar {% data variables.product.prodname_github_connect %}, puedes sincronizar el uso de licencia manualmente si subes un archivo desde {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
Cuando sincronizas el uso de licencia, solo la ID de usuario y las direcciones de correo electrónico de cada cuenta de usuario en {% data variables.product.prodname_ghe_server %} se transmiten a {% data variables.product.prodname_ghe_cloud %}.
|
||||
|
||||
{% data reusables.enterprise-licensing.view-consumed-licenses %}
|
||||
|
||||
{% data reusables.enterprise-licensing.verified-domains-license-sync %}
|
||||
|
|
@ -45,7 +47,7 @@ Después de que habilites {% data variables.product.prodname_github_connect %},
|
|||
|
||||
## Cargar el uso de licencia de GitHub Enterprise Server manualmente
|
||||
|
||||
Puedes descargar un archivo JSON desde {% data variables.product.prodname_ghe_server %} y subir el archivo a {% data variables.product.prodname_ghe_cloud %} para sincronizar de forma manual el uso de la licencia de usuario entre dos implementaciones.
|
||||
Puedes descargar un archivo JSON desde {% data variables.product.prodname_ghe_server %} y subir el archivo a {% data variables.product.prodname_ghe_cloud %} para sincronizar el uso de la licencia de usuario entre dos implementaciones de forma manual.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
|
|
|
|||
|
|
@ -14,32 +14,57 @@ shortTitle: Troubleshoot license usage
|
|||
|
||||
## About unexpected license usage
|
||||
|
||||
If the number of consumed licenses for your enterprise is unexpected, you can review your consumed license report to audit your license usage across all your enterprise deployments and subscriptions. If you find errors, you can try troubleshooting steps. Para obtener más información sobre cómo ver tu uso de licencia, consulta la sección "[Ver el uso de licencia para GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" y "[Ver la suscripción y el uso de tu cuenta empresarial](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)".
|
||||
If the number of consumed licenses for your enterprise is unexpected, you can review your consumed license report to audit your license usage across all your enterprise deployments and subscriptions. For more information, see "[Viewing license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" and "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
|
||||
|
||||
For privacy reasons, enterprise owners cannot directly access the details of user accounts.
|
||||
If you find errors, you can try troubleshooting steps.
|
||||
|
||||
For privacy reasons, enterprise owners cannot directly access the details of user accounts unless you use {% data variables.product.prodname_emus %}.
|
||||
|
||||
## About the calculation of consumed licenses
|
||||
|
||||
{% data variables.product.company_short %} bills for each person who uses deployments of {% data variables.product.prodname_ghe_server %}, is a member of an organization on {% data variables.product.prodname_ghe_cloud %}, or is a {% data variables.product.prodname_vs_subscriber %}. For more information about the people in your enterprise who are counted as consuming a license, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)."
|
||||
{% data variables.product.company_short %} bills for each person who uses deployments of {% data variables.product.prodname_ghe_server %}, is a member of one of your organizations on {% data variables.product.prodname_ghe_cloud %}, or is a {% data variables.product.prodname_vs_subscriber %}. For more information about the people in your enterprise who consume a license, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)."
|
||||
|
||||
{% data reusables.enterprise-licensing.about-license-sync %}
|
||||
For each user to consume a single seat regardless of how many deployments they use, you must synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Sincronizar el uso de licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)".
|
||||
|
||||
After you synchronize license usage, {% data variables.product.prodname_dotcom %} matches user accounts on {% data variables.product.prodname_ghe_server %} with user accounts on {% data variables.product.prodname_ghe_cloud %} by email address.
|
||||
|
||||
First, we first check the primary email address of each user on {% data variables.product.prodname_ghe_server %}. Then, we attempt to match that address with the email address for a user account on {% data variables.product.prodname_ghe_cloud %}. If your enterprise uses SAML SSO, we first check the following SAML attributes for email addresses.
|
||||
|
||||
- `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`
|
||||
- `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress`
|
||||
- `nombre de usuario`
|
||||
- `ID del nombre`
|
||||
- `emails`
|
||||
|
||||
If no email addresses found in these attributes match the primary email address on {% data variables.product.prodname_ghe_server %}, or if your enterprise doesn't use SAML SSO, we then check each of the user's verified email addresses on {% data variables.product.prodname_ghe_cloud %}. Para obtener más información sobre la verificación de las direcciones de correo electrónico de {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Verificar tu dirección de correo electrónico](/enterprise-cloud@latest/get-started/signing-up-for-github/verifying-your-email-address){% ifversion not ghec %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
|
||||
|
||||
## Fields in the consumed license files
|
||||
|
||||
The {% data variables.product.prodname_dotcom_the_website %} license usage report and {% data variables.product.prodname_ghe_server %} exported license usage file include a variety of fields to help you troubleshoot license usage for your enterprise.
|
||||
|
||||
### {% data variables.product.prodname_dotcom_the_website %} license usage report (CSV file)
|
||||
|
||||
The license usage report for your enterprise is a CSV file that contains the following information about members of your enterprise. Some fields are specific to your {% data variables.product.prodname_ghe_cloud %} (GHEC) deployment, {% data variables.product.prodname_ghe_server %} (GHES) connected environments, or your {% data variables.product.prodname_vs %} subscriptions (VSS) with GitHub Enterprise.
|
||||
|
||||
| Campo | Descripción |
|
||||
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Nombre | First and last name for the user's account on GHEC. |
|
||||
| Handle or email | GHEC username, or the email address associated with the user's account on GHES. |
|
||||
| Profile link | Link to the {% data variables.product.prodname_dotcom_the_website %} profile page for the user's account on GHEC. |
|
||||
| License type | Can be one of: `Visual Studio subscription` or `Enterprise`. |
|
||||
| License status | Identifies if a user account on {% data variables.product.prodname_dotcom_the_website %} successfully matched either a {% data variables.product.prodname_vs_subscriber %} or GHES user.<br><br>Can be one of: `Matched`, `Pending Invitation`, `Server Only`, blank. |
|
||||
| Member roles | For each of the organizations the user belongs to on GHEC, the organization name and the person's role in that organization (`Owner` or `Member`) separated by a colon<br><br>Each organization is delimited by a comma. |
|
||||
| Roles en la empresa | Can be one of: `Owner` or `Member`. |
|
||||
| Campo | Descripción |
|
||||
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| github_com_login | The username for the user's GHEC account |
|
||||
| github_com_name | The display name for the user's GHEC account |
|
||||
| github_com_profile | The URL for the user's profile page on GHEC |
|
||||
| github_com_user | Whether or not the user has an account on GHEC |
|
||||
| github_com_member_roles | For each of the organizations the user belongs to on GHEC, the organization name and the user's role in that organization (`Owner` or `Member`) separated by a colon<br><br>Organizations delimited by commas |
|
||||
| github_com_enterprise_role | Can be one of: `Owner`, `Member`, or `Outside collaborator` |
|
||||
| github_com_verified_domain_emails | All email addresses associated with the user's GHEC account that match your enterprise's verified domains |
|
||||
| github_com_saml_name_id | The SAML username |
|
||||
| github_com_orgs_with_pending_invites | All pending invitations for the user's GHEC account to join organizations within your enterprise |
|
||||
| license_type | Can be one of: `Visual Studio subscription` or `Enterprise` |
|
||||
| enterprise_server_user | Whether or not the user has at least one account on GHES |
|
||||
| enterprise_server_primary_emails | The primary email addresses associated with each of the user's GHES accounts |
|
||||
| enterprise_server_user_ids | For each of the user's GHES accounts, the account's user ID |
|
||||
| total_user_accounts | The total number of accounts the person has across both GHEC and GHES |
|
||||
| visual_studio_subscription_user | Whether or not the user is a {% data variables.product.prodname_vs_subscriber %}
|
||||
| visual_studio_subscription_email | The email address associated with the user's VSS |
|
||||
| visual_studio_license_status | Whether the Visual Studio license has been matched to a {% data variables.product.company_short %} user |
|
||||
|
||||
{% data variables.product.prodname_vs_subscriber %}s who are not yet members of at least one organization in your enterprise will be included in the report with a pending invitation status, and will be missing values for the "Name" or "Profile link" field.
|
||||
|
||||
|
|
@ -59,32 +84,16 @@ Your {% data variables.product.prodname_ghe_server %} license usage is a JSON fi
|
|||
|
||||
## Troubleshooting consumed licenses
|
||||
|
||||
If the number of consumed seats is unexpected, or if you've recently removed members from your enterprise, we recommend that you audit your license usage.
|
||||
To ensure that the each user is only consuming a single seat for different deployments and subscriptions, try the following troubleshooting steps.
|
||||
|
||||
To determine which users are currently consuming seat licenses, first try reviewing the consumed licenses report for your enterprise{% ifversion ghes %} and/or an export of your {% data variables.product.prodname_ghe_server %} license usage{% endif %} for unexpected entries.
|
||||
1. To help identify users that are consuming multiple seats, if your enterprise uses verified domains for {% data variables.product.prodname_ghe_cloud %}, review the list of enterprise members who do not have an email address from a verified domain associated with their account on {% data variables.product.prodname_dotcom_the_website %}. Often, these are the users who erroneously consume more than one licensed seat. Para obtener más información, consulta la sección "[Ver a los miembros sin un a dirección de correo electrónico desde un dominio verificado](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain)".
|
||||
|
||||
There are two especially common reasons for inaccurate or incorrect license seat counts.
|
||||
- The email addresses associated with a user do not match across your enterprise deployments and subscriptions.
|
||||
- An email address for a user was recently updated or verified to correct a mismatch, but a license sync job hasn't run since the update was made.
|
||||
{% note %}
|
||||
|
||||
Cuando se intenta coincidir con usuarios a lo largo de las empresas, {% data variables.product.company_short %} identifica a los individuos mediante las direcciones de correo electrónico verificadas y asociadas con sus cuentas de {% data variables.product.prodname_dotcom_the_website %} y mediante la dirección de correo electrónico asociada con su cuenta de {% data variables.product.prodname_ghe_server %}o aquella asignada al {% data variables.product.prodname_vs_subscriber %}.
|
||||
**Note:** To make troubleshooting easier, we recommend using verified domains with your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu empresa](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".
|
||||
|
||||
Your license usage is recalculated shortly after each license sync is performed. You can view the timestamp of the last license sync job, and, if a job hasn't run since an email address was updated or verified, to resolve an issue with your consumed license report you can manually trigger one. For more information, see "[Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
|
||||
|
||||
{% ifversion ghec or ghes %}
|
||||
If your enterprise uses verified domains, review the list of enterprise members who do not have an email address from a verified domain associated with their {% data variables.product.prodname_dotcom_the_website %} account. Often, these are the users who erroneously consume more than one licensed seat. Para obtener más información, consulta la sección "[Ver a los miembros sin un a dirección de correo electrónico desde un dominio verificado](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain)".
|
||||
{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** For privacy reasons, your consumed license report only includes the email address associated with a user account on {% data variables.product.prodname_dotcom_the_website %} if the address is hosted by a verified domain. For this reason, we recommend using verified domains with your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Then, if one person is erroneously consuming multiple licenses, you can more easily troubleshoot, as you will have access to the email address that is being used for license deduplication.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
If your license includes {% data variables.product.prodname_vss_ghe %} and your enterprise also includes at least one {% data variables.product.prodname_ghe_server %} connected environment, we strongly recommend using {% data variables.product.prodname_github_connect %} to automatically synchronize your license usage. For more information, see "[About Visual Studio subscriptions with GitHub Enterprise](/enterprise-cloud@latest/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)."
|
||||
|
||||
{% endif %}
|
||||
{% endnote %}
|
||||
1. After you identify users who are consuming multiple seats, make sure that the same email address is associated with all of the user's accounts. For more information about which email addresses must match, see "[About the calculation of consumed licenses](#about-the-calculation-of-consumed-licenses)."
|
||||
1. If an email address was recently updated or verified to correct a mismatch, view the timestamp of the last license sync job. If a job hasn't run since the correction was made, manually trigger a new job. For more information, see "[Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
|
||||
|
||||
If you still have questions about your consumed licenses after reviewing the troubleshooting information above, you can contact {% data variables.contact.github_support %} through the {% data variables.contact.contact_enterprise_portal %}.
|
||||
|
|
|
|||
|
|
@ -14,21 +14,20 @@ shortTitle: Ver el uso de licencia
|
|||
|
||||
## Acerca del uso de licencia para {% data variables.product.prodname_enterprise %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
Puedes ver el uso de licencia de {% data variables.product.product_name %} en {% data variables.product.product_location %}.
|
||||
|
||||
Puedes ver el uso de licencia de tu cuenta empresarial de {% data variables.product.prodname_ghe_cloud %} en {% data variables.product.prodname_dotcom_the_website %}.
|
||||
Si utilizas tanto {% data variables.product.prodname_ghe_cloud %} como {% data variables.product.prodname_ghe_server %} y sincronizas el uso de licencias entre los productos, puedes ver el uso de licencias de ambos en {% data variables.product.prodname_dotcom_the_website %}. For more information about license sync, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
|
||||
|
||||
{% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %}
|
||||
{% ifversion ghes %}
|
||||
|
||||
{% elsif ghes %}
|
||||
For more information about viewing license usage on {% data variables.product.prodname_dotcom_the_website %} and identifying when the last license sync occurred, see "[Viewing license usage for {% data variables.product.prodname_enterprise %}](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
|
||||
|
||||
Puedes ver el uso de licencia de {% data variables.product.prodname_ghe_server %} en {% data variables.product.product_location %}.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} Para obtener más información sobre la forma en la que se muestra el uso de licencia en {% data variables.product.prodname_dotcom_the_website %} e identificar cuándo ocurrió la última sincronización de licencia, consutla la sección "[Ver el uso de licencia para {% data variables.product.prodname_enterprise %}](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" en la documentación de {% data variables.product.prodname_ghe_cloud %}.
|
||||
You can also use the REST API to return consumed licenses data and the status of the license sync job. For more information, see "[GitHub Enterprise administration](/enterprise-cloud@latest/rest/enterprise-admin/license)" in the REST API documentation.
|
||||
|
||||
Para aprender más sobre los datos de licencia asociados con tu cuenta empresarial y de cómo se calcula la cantidad de plazas de usuario consumidas, consulta la sección "[Solucionar problemas de uso de licencia para GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Ver el uso de licencia en {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}
|
||||
|
||||
|
|
|
|||
|
|
@ -18,26 +18,26 @@ Predeterminadamente, tus codespaces tienen acceso a todos los recursos en el int
|
|||
|
||||
## Conectar los recursos a una red privada
|
||||
|
||||
There are currently two methods of accessing resources on a private network within Codespaces.
|
||||
- Using a {% data variables.product.prodname_cli %} extension to configure your local machine as a gateway to remote resources.
|
||||
- Using a VPN.
|
||||
Actualmente hay dos métodos para acceder a los recursos en una red privada dentro de Codespaces.
|
||||
- Utilizando una extensión del {% data variables.product.prodname_cli %} para configurar tu máquina local como una puerta de enlace a los recursos remotos.
|
||||
- Utilizando una VPN.
|
||||
|
||||
### Using the GitHub CLI extension to access remote resources
|
||||
### Utilizar la extensión del CLI de GitHub para acceder a los recursos remotos
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: The {% data variables.product.prodname_cli %} extension is currently in beta and subject to change.
|
||||
**Nota**: La extensión del {% data variables.product.prodname_cli %} se encuentra actualmente en beta y está sujeta a cambios.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
The {% data variables.product.prodname_cli %} extension allows you to create a bridge between a codespace and your local machine, so that the codespace can access any remote resource that is accessible from your machine. The codespace uses your local machine as a network gateway to reach those resources. For more information, see "[Using {% data variables.product.prodname_cli %} to access remote resources](https://github.com/github/gh-net#codespaces-network-bridge)."
|
||||
La extensión del {% data variables.product.prodname_cli %} te permite crear un puente entre un codespace y tu máquina local, para que el codespace pueda acceder a cualquier solución remota a la cuál se pueda acceder desde tu máquina. El codespace utiliza tu máquina local como una puerta de enlace de red para llegar a esos recursos. Para obtener más información, consulta la sección "[Utilizar el {% data variables.product.prodname_cli %} para acceder a los recursos remotos](https://github.com/github/gh-net#codespaces-network-bridge)".
|
||||
|
||||
|
||||
|
||||
|
||||
### Utilizar una VPN para acceder a los recursos detrás de una red privada
|
||||
|
||||
As an alternative to the {% data variables.product.prodname_cli %} extension, you can use a VPN to access resources behind a private network from within your codespace.
|
||||
Como alternativa a la extensión del {% data variables.product.prodname_cli %}, puedes utilizar una VPN para acceder a los recursos detrás de una red privada desde dentro de tu codespace.
|
||||
|
||||
Te recomendamos herramientas de VPN como [Open VPN](https://openvpn.net/) para acceder a los recursos de una red privada. Para obtener más información, consulta la sección "[Utilizar el cliente de OpenVPN desde GitHub Codespaces](https://github.com/codespaces-contrib/codespaces-openvpn)".
|
||||
|
||||
|
|
|
|||
|
|
@ -4,6 +4,8 @@ intro: La API de licencias proporciona información sobre tu licencia empresaria
|
|||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
fpt: '*'
|
||||
topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ sections:
|
|||
heading: La seguridad del dependabot y las actualizaciones de versión están en beta público
|
||||
notes:
|
||||
- |
|
||||
{% data variables.product.prodname_dependabot %} is now available in {% data variables.product.prodname_ghe_server %} 3.4 as a public beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_dependabot %} to be enabled by an administrator. Beta feedback and suggestions can be shared in the [{% data variables.product.prodname_dependabot %} Feedback GitHub discussion](https://github.com/community/community/discussions/categories/dependabot). For more information and to try the beta, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
|
||||
El {% data variables.product.prodname_dependabot %} ahora está disponible en {% data variables.product.prodname_ghe_server %} 3.4 como un beta público, ofreciendo actualizaciones de versión y de seguridad para varios ecosistemas populares. El {% data variables.product.prodname_dependabot %} en {% data variables.product.prodname_ghe_server %} requiere {% data variables.product.prodname_actions %} y un conjunto de ejecutores auto-hospedados configurados para que los utilice el {% data variables.product.prodname_dependabot %}. El {% data variables.product.prodname_dependabot %} en {% data variables.product.prodname_ghe_server %} también requiere de {% data variables.product.prodname_github_connect %} y de que un administrador habilite al {% data variables.product.prodname_dependabot %}. La retroalimentación y sugerencias de la versión beta pueden compartirse en el [Debate de GitHub para la retroalimentación sobre el {% data variables.product.prodname_dependabot %}] (https://github.com/community/community/discussions/categories/dependabot). Para obtener más información y para probar la versión beta, consulta la sección "[Configurar la seguridad y actualizaciones de versión del {% data variables.product.prodname_dependabot %} en tu empresa](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)".
|
||||
-
|
||||
heading: La autenticación de SAML es compatible con las aserciones cifradas
|
||||
notes:
|
||||
|
|
|
|||
|
|
@ -1,3 +1 @@
|
|||
Para que una persona que utiliza varios ambientes de {% data variables.product.prodname_enterprise %} consuma una licencia única, debes sincronizar el uso de licencias entre ambientes. Entonces, {% data variables.product.company_short %} dejará de duplicar a los usuarios con base en las direcciones de correo electrónico asociadas con sus cuentas de usuario. Las cuentas de usuario múltiples consumirán una sola licencia cuando haya una coincidencia entre la dirección de correo electrónico principal en {% data variables.product.prodname_ghe_server %} o con una dirección de correo electrónico verificad de una cuenta de {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información sobre la verificación de las direcciones de correo electrónico de {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Verificar tu dirección de correo electrónico](/enterprise-cloud@latest/get-started/signing-up-for-github/verifying-your-email-address){% ifversion not ghec %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}
|
||||
|
||||
Cuando sincronizas el uso de licencia, solo la ID de usuario y las direcciones de correo electrónico de cada cuenta de usuario en {% data variables.product.prodname_ghe_server %} se transmiten a {% data variables.product.prodname_ghe_cloud %}.
|
||||
Para que una persona que utiliza varios ambientes de {% data variables.product.prodname_enterprise %} consuma una licencia única, debes sincronizar el uso de licencias entre ambientes. Entonces, {% data variables.product.company_short %} dejará de duplicar a los usuarios con base en las direcciones de correo electrónico asociadas con sus cuentas de usuario. For more information, see "[Troubleshooting license usage for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise#about-the-calculation-of-consumed-licenses)."
|
||||
|
|
@ -1,3 +1,3 @@
|
|||
{% data variables.product.company_short %} uses a unique-user licensing model. For enterprise products that include multiple deployment options, {% data variables.product.company_short %} determines how many licensed seats you're consuming based on the number of unique users across all your deployments.
|
||||
|
||||
Each user account only consumes one license, no matter how many {% data variables.product.prodname_ghe_server %} instances the user account uses, or how many organizations the user account is a member of on {% data variables.product.prodname_ghe_cloud %}. This model allows each person to use multiple {% data variables.product.prodname_enterprise %} deployments without incurring extra costs.
|
||||
Each user only consumes one license, no matter how many {% data variables.product.prodname_ghe_server %} instances the user uses, or how many organizations the user is a member of on {% data variables.product.prodname_ghe_cloud %}. This model allows each person to use multiple {% data variables.product.prodname_enterprise %} deployments without incurring extra costs.
|
||||
|
|
|
|||
|
|
@ -1 +0,0 @@
|
|||
Si utilizas tanto {% data variables.product.prodname_ghe_cloud %} como {% data variables.product.prodname_ghe_server %} y sincronizas el uso de licencias entre los productos, puedes ver el uso de licencias de ambos en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección {% ifversion fpt or ghec %}"[Sincronizar el uso de licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Sincronizar el uso de licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)".{% endif %}
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
Antes de que puedas autorizar un token de acceso personal o llave SSH, debes haber vinculado una identidad de SAML. Si eres miembro de una organización en donde está habilitado el SSO de SAML, puedes crear una identidad vinculada autenticándote en tu organización con tu IdP por lo menos una vez. Para obtener más información, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)".
|
||||
|
||||
Después de autorizar un token de acceso personal o llave SSH. El token o llave permanecerá autorizado hasta que se revoque en una de estas formas.
|
||||
After you authorize a personal access token or SSH key, the token or key will stay authorized until revoked in one of the following ways.
|
||||
- Un propietario de empresa u organización revoca la autorización.
|
||||
- Se te elimina de la organización.
|
||||
- Se editan los alcances en un token de acceso personal o este se regenera.
|
||||
|
|
|
|||
|
|
@ -2,6 +2,6 @@ Si configuras el SSO de SAML, los miembros de tu organización seguirán inician
|
|||
|
||||
{% note %}
|
||||
|
||||
**Note:** SAML SSO does not replace the normal sign-in process for {% data variables.product.prodname_dotcom %}. Unless you use {% data variables.product.prodname_emus %}, members will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}, and each personal account will be linked to an external identity in your IdP.
|
||||
**Nota:** El SSO de SAML no reemplaza al proceso de inicio de sesión normal para {% data variables.product.prodname_dotcom %}. A menos de que utilices {% data variables.product.prodname_emus %}, los miembros seguirán iniciando sesión en sus cuenta spersonales de {% data variables.product.prodname_dotcom_the_website %} y cada cuenta personal se enlazará a una identidad externa en tu IdP.
|
||||
|
||||
{% endnote %}
|
||||
|
|
@ -13,7 +13,7 @@
|
|||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
Azure | Llave Cuenta de Almacenamiento de Azure | azure_storage_account_key{% endif %} Checkout.com | Llave de Secreto de Producción de Checkout.com | checkout_production_secret_key Clojars | Token de Despliegue de Clojars | clojars_deploy_token Databricks | Token de Acceso a Databricks | databricks_access_token DigitalOcean | Token de Acceso Personal a DigitalOcean | digitalocean_personal_access_token DigitalOcean | Token OAuth de DigitalOcean | digitalocean_oauth_token DigitalOcean | Token de Actualización de DigitalOcean | digitalocean_refresh_token DigitalOcean | Token de Sistema de DigitalOcean | digitalocean_system_token Discord | Token del Bot de Discord | discord_bot_token Doppler | Token Personal de Doppler | doppler_personal_token Doppler | Token de Servicio de Doppler | doppler_service_token Doppler | Token de CLI de Doppler | doppler_cli_token Doppler | Token de SCIM de Doppler | doppler_scim_token Doppler | Token de Auditoría de Doppler | doppler_audit_token Dropbox | Token de Acceso de Vida Corta a Dropbox | dropbox_short_lived_access_token Duffel | Token de Acceso en Vivo a Duffel | duffel_live_access_token EasyPost | Llave de la API de Producción de EasyPost | easypost_production_api_key Flutterwave | Llave de Secreto de la API en Vivo de Flutterwave | flutterwave_live_api_secret_key Fullstory | Llave de la API de FullStory | fullstory_api_key GitHub | Token de Acceso Personal a GitHub | github_personal_access_token GitHub | Token de Acceso OAuth a GitHub | github_oauth_access_token GitHub | Token de Actualización de GitHub | github_refresh_token GitHub | Token de Acceso a la Instalación de la Aplicación de GitHub | github_app_installation_access_token GitHub | Llave Privada SSH de GitHub | github_ssh_private_key Google | ID de Llave de Acceso a la Cuenta de Servicio de Almacenamiento de Google Cloud con Secreto de la Llave de Acceso de Almacenamiento de Google Cloud | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret Google | ID de Llave de Acceso de Usuario del Almacenamiento de Google Cloud con Secreto de Llave de Acceso de Almacenamiento de Google Cloud | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret Google | ID de Cliente OAuth de Google con Secreto de Cliente OAuth de Google | google_oauth_client_id </br>google_oauth_client_secret Grafana | Llave de la API de Grafana | grafana_api_key Hubspot | Llave de la API de Hubspot | hubspot_api_key Intercom | Token de Acceso de Intercom | intercom_access_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
JFrog | JFrog Platform Access Token | jfrog_platform_access_token JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} Ionic | Ionic Personal Access Token | ionic_personal_access_token Ionic | Ionic Refresh Token | ionic_refresh_token Linear | Linear API Key | linear_api_key Linear | Linear OAuth Access Token | linear_oauth_access_token Midtrans | Midtrans Production Server Key | midtrans_production_server_key New Relic | New Relic Personal API Key | new_relic_personal_api_key New Relic | New Relic REST API Key | new_relic_rest_api_key New Relic | New Relic Insights Query Key | new_relic_insights_query_key npm | npm Access Token | npm_access_token NuGet | NuGet API Key | nuget_api_key Onfido | Onfido Live API Token | onfido_live_api_token OpenAI | OpenAI API Key | openai_api_key PlanetScale | PlanetScale Database Password | planetscale_database_password PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token PlanetScale | PlanetScale Service Token | planetscale_service_token Postman | Postman API Key | postman_api_key
|
||||
JFrog | Token de Acceso a la Plataforma de JFrog | jfrog_platform_access_token JFrog | Llave de la API de la Plataforma de JFrog | jfrog_platform_api_key{% endif %} Ionic | Token de Acceso Personal a Ionic | ionic_personal_access_token Ionic | Token de Actualización de Ionic | ionic_refresh_token Linear | Llave de la API de Linear | linear_api_key Linear | Token de Acceso OAuth a Linear | linear_oauth_access_token Midtrans | Llave del Servidor de Producción de Midtrans | midtrans_production_server_key New Relic | Llave de la API Personal de New Relic | new_relic_personal_api_key New Relic | Llavde ed la API de REST de New Relic | new_relic_rest_api_key New Relic | Llave de Consulta de Perspectivas de New Relic | new_relic_insights_query_key npm | Token de Acceso a npm | npm_access_token NuGet | Llave de la API de NuGet | nuget_api_key Onfido | Token de la API en Vivo de Onfido | onfido_live_api_token OpenAI | Llave de la API de OpenAI | openai_api_key PlanetScale | Contraseña de la Base de Datos de PlanetScale | planetscale_database_password PlanetScale | Token OAuth de PlanetScale | planetscale_oauth_token PlanetScale | Token de Servicio de PlanetScale | planetscale_service_token Postman | Llave de la API de Postman | postman_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
Prefect | Prefect Server API Key | prefect_server_api_key Prefect | Prefect User API Key | prefect_user_api_key{% endif %} Proctorio | Proctorio Secret Key | proctorio_secret_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %}
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче