Re: [rest-assured] RestAssured limitation with self signed certificates

[Johan Haleby]

Thanks, great stuff. It would be very cool if you could integrate this into Rest Assured and submit a pull request. 

/Johan

On Mon, Oct 22, 2012 at 3:05 PM, Kevin Minder <kmi...@gmail.com> wrote:

I know there a limitations with RestAssured and self signed certificates.  In the hopes of getting an enhancement for that sooner rather than later I've created and attached a simple test that demonstrates at least one way to setup HttpClient+Jetty to get this to work.  Ideally I think that RestAssured would support the specification of the keystore, truststore and X509HostnameVerifier as both a request and "globally".

given()

    .keystore( "/pathToJksKeyStoreInClassPath", <password> )

    .truststore( "/pathToJksTrustStoreInClassPath", <password> )

    .hostNameVerifier( SSLSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER )

and

RestAssured.keystore( "/pathToJksKeyStoreInClassPath", <password> );

RestAssured.truststore( "/pathToJksTrustStoreInClassPath", <password> );

RestAssured.hostNameVerifier( SSLSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER );

[Pritpal Singh]

Was this added to Rest-Assured. I'm facing the same issues, struggling with it.

[Johan Haleby]

Yeah it should work, see documentation.

--
You received this message because you are subscribed to the Google Groups "REST assured" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rest-assured...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.