[
https://issues.apache.org/jira/browse/KNOX-2413?focusedWorklogId=475844&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-475844
]
ASF GitHub Bot logged work on KNOX-2413:
----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Aug/20 14:51
Start Date: 28/Aug/20 14:51
Worklog Time Spent: 10m
Work Description: smolnar82 merged pull request #367:
URL: https://github.com/apache/knox/pull/367
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 475844)
Time Spent: 40m (was: 0.5h)
> Add JWT support for HadoopAuth provider
> ---------------------------------------
>
> Key: KNOX-2413
> URL: https://issues.apache.org/jira/browse/KNOX-2413
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 1.5.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 1.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> There is a need for adding JWT support in the HadoopAuth security provider as
> follows: if the incoming request has a valid JWT token (as a {{bearer}}
> token) extracted from the {{Authorization}} header the request is then
> processed on behalf of the user represented by the JWT token (using the
> existing JWT federation provider). If there is no _valid_ JWT token, the
> {{HadoopAuth}} authentication filter should do its job as it does today.
> The ability to implement a general composite authentication provider is
> discussed in KNOX-2411, but we agreed that such a provider would need more
> planning and maybe a KIP so that this feature should be targeted in a
> separate JIRA.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
