Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usage example #9

Closed
mbajur opened this issue May 9, 2016 · 1 comment
Closed

Usage example #9

mbajur opened this issue May 9, 2016 · 1 comment

Comments

@mbajur
Copy link

mbajur commented May 9, 2016

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?

image

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
@zxr90
Copy link

zxr90 commented Jun 22, 2016

hello,

You dont need the ruby-jwt gem. You just need to specfiy the custom token generator to be used by doorkeeper.
See this https://github.com/doorkeeper-gem/doorkeeper#custom-access-token-generator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants