-
Notifications
You must be signed in to change notification settings - Fork 34
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
How to disable SSL verification in curl commands #166
Comments
Hi! That's correct, we lack initialization of the provider in |
In order to adhere to global guzzle TYPO3 settings the OAuth provider is extended to pass the necessary factories along. Related xperseguers#166
@dfineSvenFlock please test my patch as linked above. (I did not test it) |
In order to adhere to global guzzle TYPO3 settings the OAuth provider is extended to pass the necessary factories along. Related xperseguers#166
In order to adhere to global guzzle TYPO3 settings the OAuth provider is extended to pass the necessary factories along. Related xperseguers#166
Okay, |
Unfortunately it did not work. I get the same error |
Did you clear caches via Install Tool? |
I just did it. Now, i get this error:
|
Which TYPO3 version are you using? (v12 support is not yet official, my patch is v11 only) |
The reason for you error is probably this breaking change in Core: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73271/7/typo3/sysext/core/Classes/Http/Client/GuzzleClientFactory.php |
In order to adhere to global guzzle TYPO3 settings the OAuth provider is extended to pass the necessary factories along. Related xperseguers#166
I pushed a new version of the patch, which should also work with v12 |
I use v12. It works now. Thanks a lot! |
@liayn Big thanks from my side as well! I will close the issue. Please make a PR and also we are quite looking into the PR for v12 support :-). |
Hi,
I need a little help in some configuration of your extension:
I am using LetsEncrypt staging certificates for my Keycloak instance in development. Thus, I am getting the following error due to not trustworthy SSL certificates when talking to the service:
I already googled for the problem but the usual trick doesn't work:
I have verified that the setting is properly applied. Thus, I think that the plugin does not take the global setting into account or must be configured separately. I am looking for the "-k" switch in curl in our extension.
Using official LetsEncrypt certificates work fine and no error is thrown.
Can you tell me which setting I have to make?
Thanks,
Sven
The text was updated successfully, but these errors were encountered: