GitHub Enterprise Server logs error messages for failed SAML authentication in the authentication log at /var/log/github/auth.log. You can review responses in this log file, and you can also configure more verbose logging.
For more information about SAML response requirements, see "SAML configuration reference."
You can configure GitHub Enterprise Server to write verbose debug logs to /var/log/github/auth.log for every SAML authentication attempt. You may be able to troubleshoot failed authentication attempts with this extra output.
- Only enable SAML debugging temporarily, and disable debugging immediately after you finish troubleshooting. If you leave debugging enabled, the size of your log may increase much faster than usual, which can negatively impact the performance of GitHub Enterprise Server.
- Test new authentication settings for your GitHub Enterprise Server instance in a staging environment before you apply the settings in your production environment. For more information, see "Setting up a staging instance."
No canto superior � direita de GitHub Enterprise Server, clique na foto do perfil e clique em Configurações da empresa.
Na barra lateral da empresa, clique em Políticas.
Em Políticas, clique em Opções.
Under "SAML debugging", select the drop-down and click Enabled.
Attempt to sign into your GitHub Enterprise Server instance through your SAML IdP.
Review the debug output in /var/log/github/auth.log on your GitHub Enterprise Server instance.
When you're done troubleshooting, select the drop-down and click Disabled.
Some output in auth.log may be Base64-encoded. You can access the administrative shell and use the
base64 utility on your GitHub Enterprise Server instance to decode these responses. For more information, see "Accessing the administrative shell (SSH)."
$ base64 --decode ENCODED_OUTPUT
When a user signs into your GitHub Enterprise Server instance for the first time with SAML authentication, GitHub Enterprise Server creates a user account on the instance and maps the SAML
NameID to the account.
When the user signs in again, GitHub Enterprise Server compares the account's
NameID mapping to the IdP's response. If the
NameID in the IdP's response no longer matches the
NameID that GitHub Enterprise Server expects for the user, the sign-in will fail. The user will see the following message.
Another user already owns the account. Please have your administrator check the authentication log.
The message typically indicates that the person's username or email address has changed on the IdP. Ensure that the
NameID mapping for the user account on GitHub Enterprise Server matches the user's
NameID on your IdP. For more information, see "Updating a user's SAML
Recipient does not match the ACS URL for your GitHub Enterprise Server instance, one of the following two error messages will appear in the authentication log when a user attempts to authenticate.
Recipient in the SAML response must not be blank.
Recipient in the SAML response was not valid.
Ensure that you set the value for
Recipient on your IdP to the full ACS URL for your GitHub Enterprise Server instance. For example,
If your IdP does not sign the SAML response, or the signature does not match the contents, the following error message will appear in the authentication log.
SAML Response is not signed or has been modified.
Ensure that you configure signed assertions for the GitHub Enterprise Server application on your IdP.
If the IdP's response has a missing or incorrect value for
Audience, the following error message will appear in the authentication log.
Audience is invalid. Audience attribute does not match https://<em>YOUR-INSTANCE-URL</em>
Ensure that you set the value for
Audience on your IdP to the
EntityId for your GitHub Enterprise Server instance, which is the full URL to your instance. For example,
Esse erro pode ocorrer quando há uma diferença de tempo muito grande entre o IdP e o GitHub Enterprise Server, o que geralmente ocorre com IdPs auto-hospedados.
Para evitar esse problema, recomendamos apontar o dispositivo para a mesma origem do protocolo NTP que o IdP, se possível. Se você encontrar esse erro, verifique se a hora no dispositivo está sincronizada corretamente com o servidor NTP.
Se você usa o ADFS como o IdP, defina também
NotBeforeSkew no ADFS como 1 minuto para o GitHub. Se
NotBeforeSkew for definido como 0, mesmo diferenças de tempo muito pequenas, incluindo milissegundos, poderão causar problemas de autenticação.