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

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

                Author: ASF GitHub Bot
            Created on: 04/Feb/20 21:09
            Start Date: 04/Feb/20 21:09
    Worklog Time Spent: 10m 
      Work Description: moresandeep commented on pull request #252: KNOX-2207 - 
TokenStateService revocation should remove persisted token state
URL: https://github.com/apache/knox/pull/252#discussion_r374924228
 
 

 ##########
 File path: 
gateway-server/src/main/java/org/apache/knox/gateway/services/token/impl/DefaultTokenStateService.java
 ##########
 @@ -222,7 +231,7 @@ protected long getMaxLifetime(final String token) {
   }
 
   protected boolean isRevoked(final String token) {
 
 Review comment:
   Addressed in new update.
 
----------------------------------------------------------------
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: 381867)
    Time Spent: 1h 40m  (was: 1.5h)

> TokenStateService revocation should remove persisted token state
> ----------------------------------------------------------------
>
>                 Key: KNOX-2207
>                 URL: https://issues.apache.org/jira/browse/KNOX-2207
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.4.0
>            Reporter: Philip Zampino
>            Assignee: Sandeep More
>            Priority: Major
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> When the KnoxToken service is used to revoke/cancel a token, the current 
> behavior is to persist the revoked status of the token. The problem is that 
> token state is never removed from, in the case of the AliasService-based 
> implementation, the keystore. There is no real requirement to differentiate 
> between a known-but-revoked token and and unknown token; Therefore, the state 
> for a revoked token can be removed altogether.



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

Reply via email to