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
before/after successful_strategy_response not called on Token requests #1303
Comments
Is the I noticed (Regardless of the "implicit" grant flow being frown upon...) |
Could you consider this? doorkeeper/app/controllers/doorkeeper/authorizations_controller.rb Lines 88 to 97 in d84885a
How about using before/after_successful_authorization ?
before_successful_authorization do |context|
if context.pre_auth.response_type == "token"
puts "BEFORE HOOK FIRED! #{context}"
end
end
after_successful_authorization do |context|
if context.pre_auth.response_type == "token"
puts "AFTER HOOK FIRED! #{context}"
end
end
after_successful_authorization(self, auth)
def after_successful_authorization
Doorkeeper.configuration.after_successful_authorization.call(self, auth)
end |
@linhdangduy is right. Also try Doorkeeper from master branch, it has some impovements (like #1264). |
Any update here? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Manually closing staled issues without any activity and responses |
Steps to reproduce
Configure the
before_successful_strategy_response
and/orafter_successful_strategy_response
callbacks at the Doorkeeper initializer.Run an "implicit" grant flow.
Expected behavior
The configured callbacks should run.
Actual behavior
The configured callbacks are ignored.
System configuration
Running inside a Docker container, from an image based on
ruby:2.6.3-alpine
Doorkeeper initializer:
Ruby version:
ruby 2.6.3p62
Gemfile.lock:
Gemfile.lock content
The text was updated successfully, but these errors were encountered: