Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-7950

Invalid auth scheme configuration of Http client when using Kerberos (SPNEGO)



    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.10.3, 6.0
    • Fix Version/s: 5.4, 6.0
    • Component/s: None
    • Labels:


      When using kerberos authentication mechanism (SPNEGO auth scheme), the Apache Http client is incorrectly configured with all auth schemes (e.g. Basic, Digest, NTLM, Kerberos, Negotiate etc.) instead of just 'Negotiate'.

      This issue was identified after configuring Solr with both Basic + Negotiate authentication schemes simultaneously. The problem in this case is that Http client is configured with Kerberos credentials and the default (and incorrect) auth scheme configuration prefers Basic authentication over Kerberos. Since the basic authentication credentials are missing, the authentication and as a result the Http request fails. (I ran into this problem while creating a collection where there is an internal communication between Solr servers).

      The root cause for this issue is that, AbstractHttpClient::getAuthSchemes() API call prepares an AuthSchemeRegistry instance with all possible authentication schemes. Hence when we register the SPNEGO auth scheme in Solr codebase, it overrides the previous configuration for SPNEGO - but doesn't remove the other auth schemes from the client configuration. Please take a look at relevant code snippet.


      A trivial fix would be to prepare a new AuthSchemeRegistry instance configured with just SPENGO mechanism and set it in the HttpClient.


        1. solr-7950.patch
          4 kB
          Hrishikesh Gadre
        2. solr-7950-v2.patch
          4 kB
          Hrishikesh Gadre



            • Assignee:
              gchanan Gregory Chanan
              hgadre Hrishikesh Gadre
            • Votes:
              0 Vote for this issue
              5 Start watching this issue


              • Created: