[
https://issues.apache.org/jira/browse/IMPALA-10489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenzhe Zhou updated IMPALA-10489:
---------------------------------
Comment: was deleted
(was: The implementation is same as required for
[DWX-7316|https://jira.cloudera.com/browse/DWX-7316].)
> Implement JWT support
> ---------------------
>
> Key: IMPALA-10489
> URL: https://issues.apache.org/jira/browse/IMPALA-10489
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend, Clients
> Affects Versions: Impala 4.0
> Reporter: Joe McDonnell
> Assignee: Wenzhe Zhou
> Priority: Major
>
> JWT support entails:
> # Reading the JWT out of the HTTP Header
> # Verifying the JWT's signature
> # 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
