[
https://issues.apache.org/jira/browse/KNOX-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176411#comment-16176411
]
Larry McCay commented on KNOX-1060:
-----------------------------------
Hmmm, we need to be careful in this area.
The reason that it was oddly based on an implementation before rather than an
interface was that I swapped out my own implementation with nimbus. There were
some adapter type methods that bridged the nimbus JWT interface and what my
existing consumers were using. So I just made it an adapter.
If nimbus changed that then it is a really bad practice.
I have to check whether we shipped 0.13.0 with it broken now.
I would suggest that we make sure there is comprehensive unit test coverage
before refactoring such things again.
Unfortunately, I don't think there is enough in most places - adding tests has
to be the first step.
> JWT.getExpires() returns null
> -----------------------------
>
> Key: KNOX-1060
> URL: https://issues.apache.org/jira/browse/KNOX-1060
> Project: Apache Knox
> Issue Type: Bug
> Reporter: Colm O hEigeartaigh
> Priority: Minor
> Fix For: 0.14.0
>
>
> JWT.getExpires() returns null even when there is an expiry Date:
> SEVERE: Unable to parse JWT token: java.text.ParseException: The "exp" claim
> is not a String
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
