Lexikjwtauthenticationbundle: JWT: invalid signature

[flowbe]

Hello,

When I paste the token received with the login_check uri in jwt.io, it says that the signature is invalid, is it normal ?

[carlcraig]

jwt.io only supports hs256 and rs256 jwt. so f the token you are generating is different alg then it will be invalid on jwt.io.

try pasting the token using rs256 in jwt.io, and then paste the public and private keys.

[flowbe]

It's already in RS256 because of the header of the token

[carlcraig]

oki, did you paste the public/private keys into fields? i havent tried jwt.io rs feature yet, so not sure how well it works.

[flowbe]

When I paste the keys, nothing change

[carlcraig]

i have no clue then, is most likely an issue with jwt.io

[flowbe]

Is it not a problem of the token ?

[slashfan]

I tested using only the namshi/jose library and the result is the same. We'll have to investigate what is the problem, the library or the jwt.io decoding. Anyway, it is not really a problem for the moment.

[flowbe]

Thank you, I reported it just for you to know

[slashfan]

That's cool, I'll try to find the cause of the problem.

[fathimtiaz]

in the verify signature column, fill in your secret

[raesteyn]

If anyone is still running into this issue, what sorted it for me was to change the secret to match my key, then paste the token in again.

pasting the token in AFTER changing the secret is the crux of what got mine to verify.

I was using HS256.