Is the jbossws-cxf integration actually being used on client side? If that's the case, the org.jboss.security.ignoreHttpsHost being set to true should really "solve" the problem. Otherwise, setting tlsParams.setDisableCNCheck(true); programmatically might not help if the problem is during WSDL retrieval (see the discussion at https://community.jboss.org/message/811221#811221 on this).
Yes, the jbossws-cxf integration is being used on the client side. The wsdl is local, within the client war file.
It is only when System.setProperty("org.jboss.security.ignoreHttpsHost", "true") did not seem to work that I added the tlsParams.setDisableCNCheck(true) code.
The service is https enabled. The client is not. It is when the client is making a call that this is happening. Service.create(), getPort() and all works.
This was working in Jboss 7.1.1 and 7.1.3. So I was just wondering if I missed some configuration in Jboss 7.2
Thanks so much.
I have the same problem.
org.jboss.security.ignoreHttpsHost does not seem to work on JBoss 7.2.
Have you found a solotion to your problem ?
Neither of these worked for me.
I read somewhere that System.setProperty has random issues, it does not always work.
The JAVA_OPT solution did not work either.
I had to switch to Spring-WS because there was a bug in an underlying apache library, wss4j I think, in CXF at that time, related to SAML.
I had to implement a Spring-WS method to turn off hostname checking.
I had the same problem also. After hours of debugging i decided that is a bug in Jboss 7.2 and cxf integration. I replaced the cxf module(and also woodstox) in Jboss 7.2 with the one from Jboss 8 and it works now.