-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Assertion grant extension #870
Comments
Thank you! Do you think it's good to add this to a wiki, so we can leave it as documentation that can be kept up to date? |
No problem, thank you for maintaining doorkeeper, it's a fantastic library! You're welcome to add this to the wiki, or I'm happy to do it if you'd like me to. Alternatively, it could make sense to do a pull request on https://github.com/doorkeeper-gem/doorkeeper-grants_assertion, but I'm a little uncomfortable making the PR, since I haven't written any RSpec specs (or authored a ruby gem) yet. Let me know how I can help! |
I'm glad it's useful!
Please do! :) Create from https://github.com/doorkeeper-gem/doorkeeper/wiki/_new, and then link from https://github.com/doorkeeper-gem/doorkeeper/wiki/Home/_edit.
Everyone of us sent a PR to an Open Source project with it being the first time we write for a certain testing library! :) You should be fine. This project though doesn't have any maintainer, so you won't get code reviews or merge. :-/ Thank you for your help! |
Thanks! |
I found the assertion library born of #249 located at https://github.com/doorkeeper-gem/doorkeeper-grants_assertion to be out of date, and malfunctional. As such, here's a proposed extension for anyone wishing to use doorkeeper with the assertion grant_type.
After
gem doorkeeper
andbundle install
I added/modified these files to my Rails project. I based the implementation off that of the password strategy.Edit: This is not a comprehensive solution, and you'll probably need to implement some of your own authentication logic in
resource_owner_from_assertion
The text was updated successfully, but these errors were encountered: