I have tried adding the below parameters to server.xml (in ‘\jboss-soa-p-5\jboss-as\server\default\deploy\jbossweb.sar’). We are using the sample key store and trust store generated
by ‘webservice_proxy_security´ example in ‘\samples\quickstarts\’.
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
maxThreads="150" scheme="https" secure="true"
but still the endpoint is created on http protocol. . Kindly provide information on exposing Jboss ESB Service as webservice (SOAP over HTTPs) and samples if any.
wsAdapter.esb.zip 11.4 KB
What you did was the right thing to do to expose HTTPS for JBossWeb. EBWS does support HTTPS. The contract page however have an issue with listing the contracts with HTTPS protocols and the soap:address does not get transformed as such, when accessed with the https urls. But if you access the same endpoints with the HTTPS urls they still will work. I have created a JIRA here to handle this annoying issue:
Thanks for the response.
I am able to access the end point with https like https://loalhost:8443/wsAdapter/ebws/webServiceConsumeCat1/webServiceConsume1
But it is working like a normal http url. When i try to invoke the web service from soapUI its not prompting for any authentication or any certs.
where as If i expose a jboss simple web service with below security contraints in web.xml
The wsdl is created with end point as https://locahost:8443/../.. and in soap UI it prompts for authentication.
Is there any way i can include/do the similar configuration in ESB service.
Thanks Magesh, the actual requirement is to expose an esb as webservice using soap over https and as per my understanding I need to use Jboss ws to use a SOAPProcessor.
I need EBWS over HTTPS to solve the requirement. I would be checking the JIRA for updates on it.