[
https://issues.apache.org/jira/browse/KNOX-2228?focusedWorklogId=384548&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-384548
]
ASF GitHub Bot logged work on KNOX-2228:
----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Feb/20 16:40
Start Date: 10/Feb/20 16:40
Worklog Time Spent: 10m
Work Description: risdenk commented on pull request #260: KNOX-2228 -
JWTFilter should handle unknown token exception from tokeā¦
URL: https://github.com/apache/knox/pull/260#discussion_r377179358
##########
File path:
gateway-provider-security-jwt/src/main/java/org/apache/knox/gateway/provider/federation/jwt/JWTMessages.java
##########
@@ -41,6 +41,9 @@
@Message( level = MessageLevel.INFO, text = "Unable to verify token: {0}" )
void unableToVerifyToken(@StackTrace( level = MessageLevel.ERROR) Exception
e);
+ @Message( level = MessageLevel.ERROR, text = "Unable to verify token
expiration: {0}" )
Review comment:
INFO or WARN should be good I think. I just saw the message above about
unable to verify being INFO and was like hmmm that seems worse than not being
able to verify the expiration.
----------------------------------------------------------------
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: 384548)
Time Spent: 50m (was: 40m)
> JWTFilter should handle unknown token exception from token state service
> ------------------------------------------------------------------------
>
> Key: KNOX-2228
> URL: https://issues.apache.org/jira/browse/KNOX-2228
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.4.0
> Reporter: Philip Zampino
> Assignee: Philip Zampino
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When server-managed token state is enabled, and the JWT filters check if the
> token is still valid, it should not throw the exception since it results in a
> HTTP 500 response.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)