Este contenido no está disponible en el idioma seleccionado.
A.3. Troubleshooting Firefox Kerberos Configuration
If Kerberos authentication is not working, turn on verbose logging for the authentication process.
- Close all instances of Firefox.
- In a command prompt, export values for the
NSPR_LOG_*variables:export NSPR_LOG_MODULES=negotiateauth:5 export NSPR_LOG_FILE=/tmp/moz.log
- Restart Firefox from that shell, and visit the website where Kerberos authentication is failing.
- Check the
/tmp/moz.logfile for error messages with nsNegotiateAuth in the message.
There are several common errors that occur with Kerberos authentication.
- No credentials found
-1208550944[90039d0]: entering nsNegotiateAuth::GetNextToken() -1208550944[90039d0]: gss_init_sec_context() failed: Miscellaneous failure No credentials cache found
This means that no Kerberos tickets are available (meaning that they expired or were not generated). To fix this, runkinitto generate the Kerberos ticket, and then open the website again.- Server not found in Kerberos database
-1208994096[8d683d8]: entering nsAuthGSSAPI::GetNextToken() -1208994096[8d683d8]: gss_init_sec_context() failed: Miscellaneous failure Server not found in Kerberos database
This means that the browser is unable to contact the KDC. This is usually a Kerberos configuration problem. The correct entries must be in the[domain_realm]section of the/etc/krb5.conffile to identify the domain. For example:.example.com = EXAMPLE.COM example.com = EXAMPLE.COM
- No errors are present in the log
- An HTTP proxy server could be stripping off the HTTP headers required for Kerberos authentication. Try to connect to the site using HTTPS, which allows the request to pass through unmodified.
