1 Reply Latest reply on Oct 9, 2013 8:47 AM by lostvicking

    Enabling SSL for web services

    lostvicking

      Hi everyone,

       

      I'm trying to enable SSL for a web service deployed to JBoss AS 7.2.0, following the guide from https://docs.jboss.org/author/display/AS71/SSL+setup+guide but the web service is still getting deployed to http://<ip_address>:8080 and there is nothing at https://<ip_address>:8443

       

      I feel like I am missing something somewhere but all my Googling has not turned up any leads.

       

      Snippet from standalone.xml:

       

      <subsystem xmlns="urn:jboss:domain:web:1.4" default-virtual-server="default-host" native="false">

                  <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>

        <connector name="https" scheme="https" protocol="HTTP/1.1" socket-binding="https" enable-lookups="false" secure="true">

        <ssl name="f4698010" password="changeit" protocol="TLSv1" key-alias="f4698010" certificate-key-file="D:\Users\f4698010\mykeystore\f4698010.keystore" />

        </connector>

                  <virtual-server name="default-host" enable-welcome-root="true">

                      <alias name="localhost"/>

                      <alias name="example.com"/>

                  </virtual-server>

      </subsystem>

       

       

      <subsystem xmlns="urn:jboss:domain:webservices:1.2">

                  <modify-wsdl-address>true</modify-wsdl-address>

                  <wsdl-host>${jboss.bind.address:10.202.15.40}</wsdl-host>

                  <endpoint-config name="Standard-Endpoint-Config"/>

                  <endpoint-config name="Recording-Endpoint-Config">

                      <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">

                          <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>

                      </pre-handler-chain>

                  </endpoint-config>

                  <client-config name="Standard-Client-Config"/>

      </subsystem>

       

      <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">

              <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>

              <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>

              <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>

              <socket-binding name="ajp" port="8009"/>

              <socket-binding name="http" port="8080"/>

              <socket-binding name="https" port="8443"/>

              <socket-binding name="messaging" port="5445"/>

              <socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>

              <socket-binding name="messaging-throughput" port="5455"/>

              <socket-binding name="remoting" port="4447"/>

              <socket-binding name="txn-recovery-environment" port="4712"/>

              <socket-binding name="txn-status-manager" port="4713"/>

              <outbound-socket-binding name="mail-smtp">

                  <remote-destination host="localhost" port="25"/>

              </outbound-socket-binding>

          </socket-binding-group>

       

       

      Any advice would be great.

       

      Regards and thanks

      Victor

        • 1. Re: Enabling SSL for web services
          lostvicking

          Turns out this was caused by me using a self signed certificate which is not trusted by Chrome, I was testing the SSL via Advanced REST Client in Chrome and did not click 'Proceed Anyway' in order to get it ignore the fact that it's not a trusted certificate.