Question

I am migrating a application that curently runs on a Tomcat Sever to WebLogic cluster and I have found a very specific problem.

This application has a WebService that can, if so is the client will, run with SSL. We accomplish that on Tomcat by configuring the proper valve and redirecting all HTTP requests to HTTPS. This way, our WSDL will have the correct port address to be accessed through HTTPS as follows:

<port name="WebServidorWSPort" binding="tns:WebServidorWSPortBinding">
    <soap:address location="https://tomcat:8443/WebServidor/WebServidorWS"/>
</port>

I have done a similar configuration on our WebLogic cluster, and I am able to access the WSLD through HTTPS, but the port declaration still is nor right as in the snipped WSLD below:

 <port name="WebServidorWSPort" binding="tns:WebServidorWSPortBinding">
     <soap:address location="http://weblogic:8000/WebServidor/WebServidorWS"/>
 </port>

It is kind of using the HTTP front-end configuration, even with the HTTPS frontend configured. And when accessing this URL I get a HTTP 302 to the HTTPS address, rising an error on the client application.

How should I configure the server or the application to correct generate the port with the HTTPS address?

Was it helpful?

Solution

To accomplish this configuration, I had to upgrade my web.xml to Servlet 3.0 specification.

This way, on the administration console, by selecting the application I can know access a option to configure the deployed Web Services, and on Configuration > WS-Policy I can add configure TLS security.

Here is a link to use as reference:

Oracle WebLogic documentation - How to configure WS-Policy

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top