Skip to content

Docs: Add troubleshooting about Krb5Auth error 'No credentials cache found'

Katrin Leinweber requested to merge docs-troubleshoot-Krb5Auth-500-error into master

What does this MR do?

Documents a customer-confirmed workaround against this (apparently rare) error:

Completed 500 Internal Server Error in 126ms (ActiveRecord: 13.9ms | Elasticsearch: 0.0ms | Allocations: 6557)
  
Krb5Auth::Krb5::Exception (No credentials cache found):
  
ee/lib/gitlab/kerberos/authentication.rb:43:in `get_default_principal'
ee/lib/gitlab/kerberos/authentication.rb:43:in `login'
ee/lib/gitlab/kerberos/authentication.rb:19:in `login'
ee/lib/ee/gitlab/auth.rb:11:in `find_with_user_password'
lib/gitlab/auth.rb:172:in `user_with_password_for_git'
lib/gitlab/auth.rb:55:in `find_for_git_client'
app/controllers/repositories/git_http_client_controller.rb:118:in `handle_basic_authentication'
app/controllers/repositories/git_http_client_controller.rb:41:in `authenticate_user'
ee/app/controllers/ee/repositories/git_http_controller.rb:70:in `authenticate_user'
lib/gitlab/metrics/elasticsearch_rack_middleware.rb:16:in `call'
lib/gitlab/middleware/rails_queue_duration.rb:33:in `call'
lib/gitlab/metrics/rack_middleware.rb:16:in `block in call'
lib/gitlab/metrics/web_transaction.rb:21:in `run'
lib/gitlab/metrics/rack_middleware.rb:16:in `call'
lib/gitlab/middleware/speedscope.rb:13:in `call'
lib/gitlab/request_profiler/middleware.rb:17:in `call'
lib/gitlab/jira/middleware.rb:19:in `call'
lib/gitlab/middleware/go.rb:20:in `call'
lib/gitlab/etag_caching/middleware.rb:21:in `call'
lib/gitlab/middleware/multipart.rb:172:in `call'
lib/gitlab/middleware/read_only/controller.rb:50:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/same_site_cookies.rb:27:in `call'
lib/gitlab/middleware/handle_malformed_strings.rb:21:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/middleware/handle_ip_spoof_attack_error.rb:25:in `call'
lib/gitlab/middleware/request_context.rb:21:in `call'
config/initializers/fix_local_cache_middleware.rb:11:in `call'
lib/gitlab/middleware/rack_multipart_tempfile_factory.rb:19:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:74:in `call'
lib/gitlab/middleware/release_env.rb:12:in `call'
Started PATCH "/api/v4/jobs/…/trace" for … at …
Started GET "/…/….git/info/refs?service=git-upload-pack" for … at …
Processing by Repositories::GitHttpController#info_refs as */*
  Parameters: {"service"=>"git-upload-pack", "repository_path"=>"…/….git"}
Filter chain halted as :authenticate_user rendered or redirected
Completed 401 Unauthorized in 22ms (Views: 1.0ms | ActiveRecord: 3.7ms | Elasticsearch: 0.0ms | Allocations: 3104)
Started GET "/…/….git/info/refs?service=git-upload-pack" for … at …

Related issues

Author's checklist

To avoid having this MR be added to code verification QA issues, don't add these labels: feature, frontend, backend, ~"bug", or database

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  • Ensure a release milestone is set.

Merge request reports