[HBASE-5050] [rest] SPNEGO-based authentication

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.98.0, 0.95.1
• Component/s: REST, security
• Hadoop Flags: Reviewed

Release Note

A new configuration "hbase.rest.authentication" is added to enable authentication. Currently, only "kerberos" is supported. You also need to specify the SPNEGO principal with configuration "hbase.rest.kerberos.spnego.principal". The keytab configured with "hbase.rest.keytab.file" should have a key for this SPNEGO principal besides the REST server principal.

• Assignee: Jimmy Xiang
• Reporter: Andrew Kyle Purtell
• Created: 16/Dec/11 08:10
• Updated: 03/Oct/14 18:55
• Resolved: 03/Jun/13 21:50

Description

Currently the REST gateway can authenticate to a HBase cluster using a preconfigured principal. This provides a limited form of secure operation where one or more gateways can be deployed with distinct principals granting appropriate levels of privilege, but the service ports must be protected through network ACLs. This is at best a stopgap.

SPNEGO is the standard mechanism for Kerberos authentication over HTTP. Enhance the REST gateway such that it provides this option, and issues requests to the HBase cluster with the established context.

Issue Links

• is related to: KNOX-8 Support HBase via HBase/Stargate
• is related to: HBASE-5291 Add Kerberos HTTP SPNEGO authentication support to HBase web consoles
• relates to: HBASE-12168 Document Rest gateway SPNEGO-based authentication for client