Serhiy Yakovyn

Looks like my suggestion does not help :(

I finally solved the issue by doing the following in rails_spec.rb: ```ruby module RSpec::Rails::FeatureCheck module_function def has_action_cable_testing? true end end require 'rspec/rails' ``` and completely removing `require 'action_cable/testing/rspec'` from that...

@palkan, it looks like `require "rspec/rails"` from `action_cable/testing/rspec` causes to load `rspec/rails/example/channel_example_group.rb` from `rspec-rails` before `has_action_cable_testing?` get a chance to be redefined to return `true` resulting in `RSpec::Rails::ChannelExampleGroup` being empty....

I have the same issue @ShalaQweghen mentioned. However, it is not about revoking expired access tokens which is not an issue but revoking refresh tokens. E.g. if a request is...

I have a workaround that requires one extra call to `export_file` to get the full error message. Whenever `client.export_file(file.id, 'application/pdf', :download_dest => StringIO.new).string` is raising an error I'm performing one...

Working on it

Moreover, introspection of such a refresh token (bound to an expired access token) will respond with a misleading `"active": false`.

I am sorry, but I have an issue with the decision made. I have the 2 scenarios: 1. The service provider sends a state to the IdP and expects it...

> As discussed above, if we modified require_state NOT to send the state parameter in the first place, would this handle this case? I'd like to keep sending the `state`...

@stanhu, the IdP (in my case it's [Clever](https://www.clever.com/)) uses the first redirect URI and sends the ID token of the user that initiated that request. UPDATE: It is similar to...