We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
token_endpoint
I believe the Omniauth_openid_connect library bypasses https_proxy env variable when contacting e.g. token_endpoint.
https_proxy
Output of ::OpenIDConnect.http_client in Rails console show that Faraday is aware of the Proxy, and no "noproxy" sites are set.
::OpenIDConnect.http_client
The text was updated successfully, but these errors were encountered:
I think this gem just calls ::OpenIDConnect::Client.new(client_options), which ends up creating Rack::OAuth2.http_client: https://github.com/nov/rack-oauth2/blob/2aedad5d7bfd6b28d29075f3a1a7d411d11a378a/lib/rack/oauth2.rb#L44-L52
::OpenIDConnect::Client.new(client_options)
Rack::OAuth2.http_client
I'm not sure how https_proxy would be bypassed here.
Sorry, something went wrong.
No branches or pull requests
I believe the Omniauth_openid_connect library bypasses
https_proxy
env variable when contacting e.g.token_endpoint
.Output of
::OpenIDConnect.http_client
in Rails console show that Faraday is aware of the Proxy, and no "noproxy" sites are set.The text was updated successfully, but these errors were encountered: