Added guzzle options to config to allow for connection options #88
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks, don't see a problem adding this. @glena |
glena
approved these changes
Dec 5, 2017
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For those unfortunate enough to be behind a proxy, verifying tokens fails as the client domain address cannot be reached (e.g. client-domain-name.eu.auth0.com)
Adding connection options to the config allows users of this repo to specify additional options on the guzzle plugin and therefore allow traffic to pass through the proxy and JWT tokens to be verified.
An example configuration:
'guzzle_options' => [ 'curl' => [CURLOPT_PROXY => 'your-proxy-address.com', CURLOPT_SSL_VERIFYPEER => true, CURLOPT_PROXYPORT => '8080', CURLOPT_PROXYUSERPWD => 'username:password']],Thanks