[
https://issues.apache.org/jira/browse/KNOX-2703?focusedWorklogId=710741&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-710741
]
ASF GitHub Bot logged work on KNOX-2703:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Jan/22 18:36
Start Date: 18/Jan/22 18:36
Worklog Time Spent: 10m
Work Description: smolnar82 merged pull request #532:
URL: https://github.com/apache/knox/pull/532
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 710741)
Time Spent: 50m (was: 40m)
> Make acceptable JWT types configurable
> --------------------------------------
>
> Key: KNOX-2703
> URL: https://issues.apache.org/jira/browse/KNOX-2703
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 1.6.0, 1.6.1, 1.6.2
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Critical
> Fix For: 2.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> With KNOX-2149, one can define their own JWKS URL which Knox can use for
> verification.
> However, the current implementation only supports JWTs with {{"typ: JWT"}} in
> their headers (or not type definition at all). In previous JOSE versions,
> there were other supported types such as {{{}at+jwt{}}}.
> It'd be beneficial to have the list of allowed JWT types defined on the
> topology level. If not defined, Knox should use the current default
> ({{{}JWT{}}}).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
