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
{{ message }}
This repository has been archived by the owner on Oct 5, 2023. It is now read-only.
If I look at the code causing the error at authorizations_controller.rb#L46 and compare that with Rack::Oauth2's token.rb#L59 then it seems Rack::Oauth2 doesn't accept the uid attribute.
Am I doing something wrong? Or has something changed in Rack::Oauth2 that is incompatible with this gem? I looked at their commits in the last few days, but couldn't find anything related to this issue.
Removing the provided line in devise_oauth2_providable "fixes" the issue, but since I don't see the uid being used anywhere I am not sure if this causes a security issue or not.
The text was updated successfully, but these errors were encountered:
This only happens when you ask for a response_type=token, it works fine if you ask for a response_type=code.
describe 'POST #create' do
context 'with valid redirect_uri' do
with :user
with :client
let(:redirect_uri) { client.redirect_uri }
before do
sign_in user
post :create, :commit => 'Approve', :approve => true, :client_id => client.identifier, :redirect_uri => redirect_uri, :response_type => 'token', :use_route => 'devise_oauth2_providable'
end
it { should respond_with :redirect }
it { should respond_with_content_type :html }
end
end
plancien
added a commit
to Toxicode/devise_oauth2_providable
that referenced
this issue
Mar 29, 2017
I'm getting an undefined_method error when I try to grant access to a Backbone app using a token.
Here's the log:
If I look at the code causing the error at authorizations_controller.rb#L46 and compare that with Rack::Oauth2's token.rb#L59 then it seems Rack::Oauth2 doesn't accept the uid attribute.
Am I doing something wrong? Or has something changed in Rack::Oauth2 that is incompatible with this gem? I looked at their commits in the last few days, but couldn't find anything related to this issue.
Removing the provided line in
devise_oauth2_providable
"fixes" the issue, but since I don't see the uid being used anywhere I am not sure if this causes a security issue or not.The text was updated successfully, but these errors were encountered: