webservice and https

[omrikessel]

How do I configure jboss to replace the:
REPLACE_WITH_ACTUAL_URL port address
with https and secure port and not with http?

[jason.greene]

Change REPLACE_WITH_ACTUAL_URL to https://REPLACE_WITH_ACTUAL_URL, and JBoss will rewrite it using https and the secure port.

-Jason

[steveh123]

Hi guys is there any other way at the moment of doing this. i would have thought the schema would have been part of the configuration deploy\jboss-ws4ee.sar\META-INF\jboss-service.xml.

This currently means we have to maintain 2 different versions of our ear file, one for customers running http and a second for one running https

Regards,
Steve

[thomas.diesler]

Jason,

looking at this, should the choice of protocol not be driven by the transport guarantie?

What if transport guarantie and the protocol in the wsdl are not in sync?

Steve,

the wsdl is the abstract contract for the web service and defines the soap:address that a port can be accessed at. So if you have two contracts you need two deployments.

Maybe it is possible for you to have both ports defined in the wsdl and disable http access in the environment the WS is deployed to.

[jason.greene]

If transport gaurantee was set then the client should still work with an http:// url because tomcat will send a 302 redirect to https://.

I think we should change the wsdl generation to use transport gaurantee as a hint. If someone wants to overide the behavior then they could disable address rewriting.

-Jason

[jason.greene]

For BC we will probably still have to support the https://REPLACE_URL methodology because it is possible for someone to not set transport gaurantee and just enable the ssl connector.

-Jason

[steveh123]

Hi Guys,
Thanks for the replies, just a quick question. If the transport guarantee is not set, is is valid to run over ssl?.. if so should it not be posible to configure the whole wsdl from the server configurations rather than from the wsdl or the deployment descripters.

I guess the short of it i feel the the HTTPS://REPLACE_WITH_ACTUAL_URL confusing because the host and port come from the from a configuration file and the schema comes from the wsdl.


Regards,
Steve

[jason.greene]

The problem with adding scheme to the server-wide configuration file is that it will be globaly applied across all webservices.

We will follow transport guarantee in 4.0.4. I have created the following JIRA issue:

http://jira.jboss.org/jira/browse/JBWS-454

-Jason