Closed lauramosher closed 2 years ago
That's unfortunate. I'll work on it as soon as possible. Feel free to submit a fix.
@waiting-for-dev After further testing, this actually looks like an issue with devise-jwt
and how it yields configuration to this gem.
I'll close this one out and open it on the proper repo!
Please, for a bug report fill in the following template. Before that, make sure to read the whole README.
Feature requests and questions about
warden-jwt_auth
are also accepted.Expected behavior
decoding_secret
to correctly default tosecret
on configuration per the README stating thatdecoding_secret
only need to be set if using an asymmetric algorithm; and devise jwt / token decoding works as expectedActual behavior
decoding_secret
is nil; devise jwt / token decoding does not work and returns "No verification key available"Steps to Reproduce the Problem
Warden::JWTAuth::TokenDecoder.new.call(<TOKEN>)
JWT::DecodeError (No verification key available)
is returnedDebugging information
Provide following information. Please, format pasted output as code. Feel free to remove the secret key value.
Version of
warden-jwt_auth
in use 0.7.0Output of
Warden::JWTAuth.config
Not, requested, but Output of
Devise::JWT.config
(0.9.0)If your issue is related with not getting a JWT from the server:
If your issue is related with not being able to revoke a JWT: