Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-10556

NPE if sasl.mechanism is unrecognized

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 2.7.0
    • None
    • None

    Description

      If a client sets an unknown sasl.mechanism value (e.g. mistakenly setting "PLAN" instead of "PLAIN") the client sees a NullPointerException that only indirectly indicates the nature of the problem. For example:

      java.lang.NullPointerException
      at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.sendSaslClientToken(SaslClientAuthenticator.java:430)

      It is better to see an exception that directly states what the issue is. For example, the initial version of this PR would provide the following information:

      Caused by: org.apache.kafka.common.errors.SaslAuthenticationException: Failed to create SaslClient with mechanism PLAN

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. KAFKA-9497 Brokers start up even if SASL provider is not loaded and throw NPE when clients connect

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. KAFKA-7631 NullPointerException when SCRAM is allowed bu ScramLoginModule is not in broker's jaas.conf

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Web Link GitHub Pull Request #9356

          Web Link GitHub Pull Request #9372

          Activity

            People

              rndgstn Ron Dagostino
              rndgstn Ron Dagostino
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: