[jira] [Work logged] (KNOX-2212) TokenStateService should fail permissively

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 25/Feb/20 21:13
            Start Date: 25/Feb/20 21:13
    Worklog Time Spent: 10m 
      Work Description: moresandeep commented on pull request #274: KNOX-2212 - Token permissiveness
URL: https://github.com/apache/knox/pull/274
 
 
   ## What changes were proposed in this pull request?
   
   When `gateway.knox.token.permissive.failure.enabled`  property is set to true in gateway-site.xml (by default it is false) **and** `knox.token.exp.server-managed` is set to true in the descriptor (server managed token state is enabled) then, when Knox encounters a valid token which is not stored in it's token state Knox uses the expiry date of the JWT token instead of flagging it as "Unknown Token"
   
   ## How was this patch tested?
   This patch was locally tested
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 392934)
    Remaining Estimate: 0h
            Time Spent: 10m

> TokenStateService should fail permissively
> ------------------------------------------
>
>                 Key: KNOX-2212
>                 URL: https://issues.apache.org/jira/browse/KNOX-2212
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.4.0
>            Reporter: Philip Zampino
>            Assignee: Sandeep More
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> While unlikely, it's possible that the TokenStateService may be presented with a token, for which it has no state, but which can be verified as a valid (origin, expiration, etc...) token. In these cases, rather than rejecting the token for lack of server-managed state, the token's state should be recorded, and the associated operation permitted.



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