Jwt-auth: Token Signature could not be verified.

[paolog22]

TokenInvalidException in NamshiAdapter.php line 71: Token Signature could not be verified.

Got this error while trying to decode Jwt Token , but decoding at jwt.io site it is fine.

any idea?
thanks

[rico]

I think it actually happens on line 84 of Namshi.php. The verify()Method of JWS.php always fails.

[wemersonjanuario]

This happens with me sporadically with no explanations When I send too many request to api some callbacks having this error "Token Signature could not be verified". If you request again everything goes ok.

I could work around this passing jwt_secret code directly on jwt.php config file instead of env('JWT_SECRET').

Do you knows if laravel middlare has a BUG using .env variables on middlares? sometimes env values return null inside middlewares.

[paolog22]

@wemersonjanuario i fixed my problem with NBF . do double check your NBF .
hope it helps :)

[wemersonjanuario]

Sorry NBF?

[wemersonjanuario]

How?

[paolog22]

@wemersonjanuario please refer here
https://github.com/tymondesigns/jwt-auth/wiki/Creating-Tokens

[wemersonjanuario]

I've understood what nbf means. But How to modify It ? I have token create automaticaly by attempt method. Can you make It more clear? Thanks

[mycarrysun]

@paolog22 I'm running into this issue as well and can't find a resolution anywhere, thinking maybe nbf could be another issue?

Can you explain what might be wrong with nbf?

[paolog22]

@mycarrysun hi can you show some logs ?
i fix my problem with the time
@wemersonjanuario hi sorry late reply been busy but do please check the time being include in the token..

[mycarrysun]

@paolog22 it was the format of the Authorization header....syntax was wrong. The package I got the starter template from was in Bearer: [token goes here] which did not work until I changed it to Bearer : [token] and worked the entire day. Something changed though because it stopped working and what fixed it was changing the format to Bearer [token].

[jegjessing]

I get token cannot be verified... If I call the API with token=[token] then the call goes just fine through it.
I can verify this by removing a character from the token which results in "Could not decode token". If I leave the token out then I get token not provided. So, JWT is working fine as such.
But when Laravel receives it from the FE code. (Angular 6) then it fails with the above message.
I send the token in header with: Authorization: Bearer "[token]" and then I get the Token could not be verified.
If I try to change the header to i.e. Authorization: "[token]" and then I get the Token not provided.
So conclusion is, that the same token cannot be verified through header but it can through URL parameter.
But why? I'm using JWT in another project, I'm using the same:
RewriteCond %{HTTP:Authorization} .
RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

I'm lost. Please help :-)
Thanks in advance!!