Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-7357

HBaseClient and HBaseServer should use hbase.security.authentication when negotiating authentication

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.94.4, 0.95.0
    • Component/s: security
    • Labels:
      None
    • Hadoop Flags:
      Incompatible change, Reviewed
    • Release Note:
      Hide
      This is a slightly incompatible change.
      HBase SASL connection negotiation is now enabled by setting hbase.security.authentication rather than hadoop.security.authentication.
      Show
      This is a slightly incompatible change. HBase SASL connection negotiation is now enabled by setting hbase.security.authentication rather than hadoop.security.authentication.

      Description

      This came up in the context of testing HBASE-6788. Currently HBaseClient and HBaseServer call UserGroupInformation.isSecurityEnabled() when determining whether or not to use SASL to negotiate connections. This means they are using the hadoop.security.authentication configuration value. Since this is in the context of HBase RPC connections, it seems more correct to use the hbase.security.authentication configuration value by calling User.isHBaseSecurityEnabled().

        Attachments

        1. HBASE-7357.patch
          4 kB
          Gary Helmling
        2. HBASE-7357_0.94.patch
          3 kB
          Gary Helmling
        3. HBASE-7357_0.94_2.patch
          3 kB
          Gary Helmling

          Issue Links

            Activity

              People

              • Assignee:
                ghelmling Gary Helmling
                Reporter:
                ghelmling Gary Helmling
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: