[ 
https://issues.apache.org/jira/browse/KNOX-2542?focusedWorklogId=564707&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-564707
 ]

ASF GitHub Bot logged work on KNOX-2542:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Mar/21 16:16
            Start Date: 11/Mar/21 16:16
    Worklog Time Spent: 10m 
      Work Description: pzampino opened a new pull request #409:
URL: https://github.com/apache/knox/pull/409


   ## What changes were proposed in this pull request?
   
   Moved token verification until after expiry evaluation, and added caching of 
successful token verification.
   
   ## How was this patch tested?
   
   Added test to AbstractJWTFilterTest, and executed existing tests.
   


----------------------------------------------------------------
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: 564707)
    Remaining Estimate: 0h
            Time Spent: 10m

> Token-based providers should check expiration before verifying tokens
> ---------------------------------------------------------------------
>
>                 Key: KNOX-2542
>                 URL: https://issues.apache.org/jira/browse/KNOX-2542
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 1.4.0
>            Reporter: Philip Zampino
>            Assignee: Philip Zampino
>            Priority: Major
>             Fix For: 1.5.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, the (expensive) token verification is done before any other token 
> validation. As performance optimization, it should rather delay the 
> verification until after the issuer and expiration have been evaluated. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to