# Kong 1.3.0 and JWT Validation

**URL:** https://discuss.konghq.com/t/kong-1-3-0-and-jwt-validation/4421
**Category:** Questions
**Created:** [September 13, 2019, 8:30am UTC](https://discuss.konghq.com/t/kong-1-3-0-and-jwt-validation/4421 "2019-09-13T08:30:19Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Thomas\_Gilbert](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/thomas_gilbert/32/1329_2.png) [@Thomas\_Gilbert](https://discuss.konghq.com/u/Thomas_Gilbert)
#### Post date: [September 13, 2019, 8:30am UTC](https://discuss.konghq.com/t/kong-1-3-0-and-jwt-validation/4421/1 "2019-09-13T08:30:19Z")

</div>

Hi,

I was using kong 0.14.1 without any problem. The gateway was configured with a global JWT plugin and all the consumers did have a JWT credential with the correct configuration.  
I recently decided to move to version 1.3.0, applied the same configuration and all my requests did fail with a 401 Unauthorized (the traffic is routed normally if I disable the JWT Plugin).  
Then, I downgraded to version 1.2.2 and the exact same configuration was working normally. As I did not find a breaking change in 1.3.0 which could lead to this problem, I was wondering what could be the reason that the latest version does not seem to work anymore for this use case.

Any feed-back is more than welcome !