oltu-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Meyer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OLTU-172) Handle invalid JWT exp field more gracefully
Date Wed, 22 Apr 2015 09:27:58 GMT

     [ https://issues.apache.org/jira/browse/OLTU-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Meyer updated OLTU-172:
------------------------------
    Attachment: JWTClaimsSetParser-Number-Cast-v1.patch

longValue() is available in super class. So always cast to Number to get the corresponding
value.

> Handle invalid JWT exp field more gracefully
> --------------------------------------------
>
>                 Key: OLTU-172
>                 URL: https://issues.apache.org/jira/browse/OLTU-172
>             Project: Apache Oltu
>          Issue Type: Bug
>          Components: oauth2-jwt
>            Reporter: Thomas Meyer
>            Priority: Minor
>         Attachments: JWTClaimsSetParser-Number-Cast-v1.patch
>
>
> Hi,
> Sadly WSO2 create invalid JW tokens with an "exp" field with millisecond resolution.
According to the spec the field "exp" should only contain second resolution.
> When JWTReader tries to parse the exp field a ClassCastException will occur, becaue a
Long object is returned and not an Integer.
> Attached patch casts to the super class method to cover Long and Integer values correctly.
> What do you think about this patch? Okay to go in?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message