Problem is with testing, not sure how we can automate testing with a web
proxy. We would require tests to be added with a PR as well as
documentation updates.
On 22 March 2017 at 19:56, Stian Thorgersen <sthorger(a)redhat.com> wrote:
It should be fixed by adding a configuration option to the
HttpConnection
provider that allows setting the proxy settings for the underlying
HttpClients. We won't accept a solution that relies on using system
properties for config, nor switching to SimpleHttp (in fact that's changed
to now use HttpConnection under the covers).
On 22 March 2017 at 09:25, Plank Martin <Martin.Plank(a)softec.sk> wrote:
> Hello,
>
> It would be nice if the ReCaptcha worked behind a corporate proxy. It was
> already reported in [1].
> The problem is that ReCaptcha validation is implemented with the use of
> Apache HttpClient, which does not respect the Java proxy settings by
> default.
> It can be fixed by using the SimpleHttp utility (which uses
> HttpURLConnection under the hood) instead of HttpClient.
> I will be happy to contribute. Would you welcome this contribution?
>
> Thank you for your answers
> Martin
>
> [1]
https://issues.jboss.org/browse/KEYCLOAK-4272
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-user
>