JWT custom claims

[klansser]

Hi,
I've found something strange in how Hydra handles custom claims in the JWT.
When I send a number larger than 1 MIL (7 digits) by accepting Consent Session (as an object in session.access_token) Hydra changes this number to double or scientific notation (with .x in the last position). This is a problem because I get it in a JWT (as ext value) where I expect an integer.

Has anyone had this kind of problem?

I'm using Hydra 1.8.x now (and it works well) but I want to update to 2.x (which has this strange behavior).