[IMPALA-10489] Implement JWT support

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 4.0.0
• Fix Version/s: Impala 4.1.0
• Component/s: Backend, Clients
• Epic Link: Impala JWT Support
• Epic Color: ghx-label-2
• Assignee: Wenzhe Zhou
• Reporter: Joe McDonnell
• Created: 08/Feb/21 19:04
• Updated: 16/Jul/21 01:30
• Resolved: 15/Jul/21 22:52

Description

JWT support entails:

1. Reading the JWT out of the HTTP Header
2. Verifying the JWT's signature
3. Getting the username out of the JWT contents

For #1, we can assume that it comes in via the Authorization: Bearer header. If this is not uniform, this may need to be configurable.

For #2, we need the public key of the entity that produced the JWT. This will need to be passed in at startup. 

For #3, there is no standardized name for the username field on a JWT. This should be configurable.

Subsequent tasks may provide other ways to specify the public key and parse out other pieces of information from the JWT.