aud_header
and scope on devise-jwt
#5841
Replies: 1 comment 1 reply
-
Sorry, this is not the right place for this question. @waiting-for-dev I don't think the devise-jwt "New Issue" button should come here. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
(the New Issue button took me here from
devise-jwt
, hope this question makes sense here)If I understand correctly, for JWTs to be valid with the
devise-jwt
plugin, I need to send the token itself on a header, and another header specifying theaud
claim value that is to be valid? The README seems to imply it's optional ("If you don't want to differentiate between clients, you don't need to provide that header.") but if it's not provided, the check inlib/warden/jwt_auth/user_decoder.rb:44
will always fail - right? I'd really like to not need this second header.Same for the
scp
claim, is there a way for it to be optional and always default to:user_account
? (line 43 of the same file).I'm trying to consume tokens generated outside of Rails. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions