5 Replies Latest reply on Aug 31, 2011 5:12 AM by isabelc

    Issue with soap:address generated (https)

    vbrich

      I'm having issues configuring jbossws to generate our wsdl with the correct endpoint location. Actually, we built this web service "contract first", so were surprised that the wsdl was being regenerated upon deployment. Now that we realize this, we are having difficulty getting our endpoint set correctly. Names have been changed to protect the innocent.

       

      This issue is simliar to http://community.jboss.org/message/336384#336384

       

      We are using:

      - JBoss EAP 5.1.0

      - JBoss Native WS stack (default)

       

      The code is deployed in jboss and accessible internally here:

      http://10.11.2.333:8280/SomeService?wsdl

       

      The web service should be publicly accessible here:

      https://somewhere.com/SomeService?wsdl

       

      Our SSL terminates at a load balancer (upstream) so the web service itself is HTTP (via JBoss).

       

      So, I can almost get the url correct by tweaking jboss-beans.xml, but can’t get the endpoint to say “https” instead of “http”…

      http://somewhere.com/SomeService?wsdl

       

      JBoss is using the default 8080 connector… and we added another one on port 8280

      <Connector protocol="HTTP/1.1" port 8080" address="${jboss.bind.address}" connectionTimeout="20000" redirectPort="8443" />

      <Connector protocol="HTTP/1.1" port 8280" address="${jboss.bind.address}" connectionTimeout="20000" redirectPort="8443" />

       

      Attempt 1 (default configuration) gives: <soap:address location="http://10.11.2.333:8280/SomeService" />

          <property>${jboss.bind.address}</property>

          <property>true</property>

         <!-- <property>8443</property> -->

         <!-- <property>8080</property> -->

       

      Attempt 2 gives: <soap:address location="http://somewhere.com:8080/SomeService " />

          <property>somewhere.com </property>

          <property>true</property>

          <property>8443</property>

          <property>8080</property>

       

      Attempt 3 gives: <soap:address location="http://somewhere.com:8280/SomeService " />

          <property>somewhere.com </property>

          <property>true</property>

          <property>8443</property>

         <!-- <property>8080</property>-->

       

      Attempt 4 gives: <soap:address location="http://somewhere.com:8280/SomeService " />

          <property>somewhere.com </property>

          <property>true</property>

         <!-- <property>8443</property>-->

         <!-- <property>8080</property>-->

       

      Attempt 5 gives: <soap:address location="http://somewhere.com:8280/SomeService " />

          <property>somewhere.com </property>

          <property>false</property>

         <!-- <property>8443</property>-->

         <!-- <property>8080</property>-->

       

      Attempt 6 gives: KABOOM starting jboss regarding web service port

          <property>somewhere.com </property>

          <property>true</property>

         <!-- <property>8443</property>-->

          <property></property>

       

      Attempt 7 gives: <soap:address location="http://somewhere.com/SomeService " />

          <property>somewhere.com</property>

          <property>true</property>

         <!-- <property>8443</property>-->

          <property>80</property>

       

      Ideas? Any help is appreciated.

        • 1. Re: Issue with soap:address generated (https)
          isabelc

          This thread is quite old now but I am facing the same problem.

           

          Up to the proxy (apache) the communication is via https. From this point on to the JBoss (4.2.3 GA) the communication is http. I was able to alter the address location showing the url, but it won't let me change it from http to https. The problem is that no client communicating via proxy can access the xsd schema of my webservice.

           

          One possibility to solve this is to change the communication between proxy and jboss to https. But for now I am searching for an easier (in my case everything else is easier) solution.

          Any ideas?

          • 2. Re: Issue with soap:address generated (https)
            jim.ma

            Can you try adding transport-gurantee to your web.xml to see if that helps ?

             

             <security-constraint>
               ...
               <user-data-constraint>
                 <transport-guarantee>CONFIDENTIAL</transport-guarantee>
               </user-data-constraint>
             </security-constraint>
            
            • 3. Re: Issue with soap:address generated (https)
              vacz

              I have exactly the same issue with Isabel: JBoss 4.2.3.GA, behind a load balancer, http between JBoss and load balancer and https between load balancer and client.

              I was not allowd to change the http connection between JBoss and load balancer to https.

              Any suggestions?

              • 4. Re: Issue with soap:address generated (https)
                isabelc

                I tried several things now:

                 

                In deploy\jbossws.sar\jbossws.beans\META-INF\jboss-benas.xml I set the webServiceHost (i don't want the customer to see the IP) and the webServiceSecurePort.

                 

                In the server.xml i configured the port:

                 

                <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
                           maxThreads="150" scheme="https" secure="true"
                           clientAuth="false" sslProtocol="TLS" />

                 

                At last i added the security-constraint like Jim suggested.

                 

                The only change is that instead of the IP i get the URL now, but still as http and not https.

                 

                Apart from that i found this Bug Report: https://issues.jboss.org/browse/JBPAPP-4648

                 

                Within this bug report I found an article about setting up https as well: http://community.jboss.org/wiki/JBossWS-SecureTransport

                But this didn't lead me anywhere as well.

                • 5. Re: Issue with soap:address generated (https)
                  isabelc

                  I'd just like to add, that I am talking about the schemaLocation we are talking about.