-
1. Re: jaxws:endpoint exposed via HTTPS
njiang Mar 23, 2011 9:13 PM (in response to gmdavidson62)If you still want to deploy the jaxws:endpoint into the Web Container, you need to configure the Web Container to provide HTTPS connection.
If not, you can take a look at the examples that Fuse SF kit has, the example name is
wsdl_first_https.
Willem
-
2. Re: jaxws:endpoint exposed via HTTPS
ffang Mar 24, 2011 1:59 AM (in response to gmdavidson62)Hi,
Since your configuration has address="/ifbisecureesb"
so I assume you deploy this jaxws:endpoint into FUSE ESB4 which use http-osgi transport underlying, which use http osgi service provided by pax-web.
So what you need is configure SSL for pax-web, more details from here[1], also we add a stub configuration file for pax-web ssl configuration in the latest released FUSE ESB 4.3.1-fuse-01-09, it's FUSE_ESB/etc/org.ops4j.pax.web.cfg, this is a stub file but you only easily adapt it for a real configration, you may need take a look.
http://wiki.ops4j.org/display/paxweb/SSL+Configuration
Freeman
-
3. Re: jaxws:endpoint exposed via HTTPS
gmdavidson62 Mar 24, 2011 1:05 PM (in response to ffang)Thank you, this is exactly what I was looking for.
This worked:
org.osgi.service.http.enabled=true
org.osgi.service.http.port=8181
org.osgi.service.http.secure.enabled=true
org.osgi.service.http.port.secure=8183
org.ops4j.pax.web.ssl.keystore=certs/myKeystore.jks
org.ops4j.pax.web.ssl.keystore.type=JKS
org.ops4j.pax.web.ssl.password=myPassword
org.ops4j.pax.web.ssl.keypassword=myPassword
org.ops4j.pax.web.ssl.clientauthwanted=false
org.ops4j.pax.web.ssl.clientauthneeded=false