[arquillian-issues] [JBoss JIRA] (ARQ-687) Support for custom hostname verifiers

[Vineet Reynolds (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vineet Reynolds updated ARQ-687:
--------------------------------

              Status: Pull Request Sent  (was: Coding In Progress)
    Git Pull Request: https://github.com/arquillian/arquillian-container-wls/pull/3


Pull request sent.

Custom hostname verifiers are now supported via the introduction of two new properties - hostnameVerifierClass & classPath.

This is used only by weblogic.Deployer and not by the JMX client, as the connection to the MBean server does not appear to require hostname verification. All SSL arguments supported by weblogic.Deployer of WLS 10.3 is now supported by the Arquillian integration.

                
> Support for custom hostname verifiers
> -------------------------------------
>
>                 Key: ARQ-687
>                 URL: https://issues.jboss.org/browse/ARQ-687
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: WebLogic Containers
>    Affects Versions: wls_1.0.0.Alpha1
>         Environment: Windows XP/Linux Open Suse , Sun JVM
>            Reporter: Shajahan Palayil
>            Assignee: Vineet Reynolds
>
> My organization has a custom TrustKeyStore which has been configured by weblogic start parameter as below.
> weblogic.security.SSL.ignoreHostnameVerifictaion=false
> weblogic.security.SS.hostNameVerifier='custom built class name goes here'
> weblogic.security.TrustKeyStore=CustomTrust
> weblogic.security.CustomTrustKeyStoreFileName='location of the .properties file here'
> weblogic.security.CustomTrustKeyStorePassPhrase='pass phrase here'
> weblogic.security.CustomTrustKeyStoreType='TYPE goes here'
> I tried JSFUnit with Arquillian on normal weblogic server (downloaded and installed from Oracle) and its working great. But when I try to run it on organization provided weblogic env, it fails with error on client side with message, "Certificate chain received from localhost was not trusted causing SSL handshake failure etc..etc.." and on server console the error message is BAD_CERTIFICATE alert was received from localhost etc..etc..
> The configuration is as below.
>  <container qualifier="wls-ssl-demotrust" default="true">
>         <configuration>
>             <property name="adminUrl">t3s://localhost:9998</property>
>             <property name="adminUserName">weblogic</property>
>             <property name="adminPassword">weblogic</property>
>             <property name="target">admin_server_name</property>
>             <property name="wlsHome">HOME DIRECTORY HERE</property>           
>              <property name="useCustomTrust">true</property>
>             <property name="trustStoreLocation">location of the .properties file here</property>
>             <property name="trustStorePassword">pass phrase here</property>
>         </configuration>
>     </container>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira