You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use that gem in my application but i can't do that. I actually don't even know if i'm doing it right. Anyway, i have a jwt token generated by ruby-jwt, using secret key of my rails app.
Sending a requests to my oauth2 api with a header Authorization: Bearer <my token> results in 401. What's weird - i can see in the server console that doorkeeper tries to find that token i'm sending in the doorkeeper tables and, if i understand JWT properly, that should not happen at all?
I would be really thankfull for any usage example or ideas on what might be wrong in my approach. Thanks in advance!
doorkeeper 3.1.0
doorkeeper-jwt 0.1.4
The text was updated successfully, but these errors were encountered:
Hello!
I'm trying to use that gem in my application but i can't do that. I actually don't even know if i'm doing it right. Anyway, i have a jwt token generated by ruby-jwt, using secret key of my rails app.
Sending a requests to my oauth2 api with a header
Authorization: Bearer <my token>
results in 401. What's weird - i can see in the server console that doorkeeper tries to find that token i'm sending in the doorkeeper tables and, if i understand JWT properly, that should not happen at all?I would be really thankfull for any usage example or ideas on what might be wrong in my approach. Thanks in advance!
The text was updated successfully, but these errors were encountered: