Allow hostname verification to be disabled through arquillian.xml

[codingchili]

Short description of what this resolves:

Allows disabling hostname verification for the WLPRestClient used in the remote adapter.

Changes proposed in this pull request:

• adds 'disableHostnameVerification', boolean: true|false as a configuration option to arquillian.xml
• hostname verification is enabled by default.
• configures the SSLContext with a trust manager that trusts all certificates.
• sets the NoopHostnameVerifier on the http client.

Fixes: #47

[aguibert]

hi, thanks for the PR!

Code changes look good, but lets change the property name from disableHostnameVerification to hostnameVerificationEnabled to avoid the double-negative.

[codingchili]

Hi, thanks!

Updating next Tuesday.

[Azquelt]

Disabling hostname verification is not the same as trusting all certificates.

If the intent is just to disable hostname verification, it needs to do just that (i.e. just the change to add the NoopHostnameVerifier).

If the intent is to allow untrusted certificates, then I think the name of the configuration parameter should be changed. Maybe something like connectionSecurityEnabled or useInsecureConnection?