Clovertech

HTTPS Server/Inbound Thread Connection

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › HTTPS Server/Inbound Thread Connection

  • Creator
    Topic
  • May 7, 2017 at 6:36 pm #55383
    Corrie Henry
    Participant

      I have a vendor who wants to connect to/send me data via HTTPS

      So I would like to setup server/inbound thread using the GUI to accept the messages.

      I have successfully setup an HTTP server thread but when I try the same steps with an HTTPS address I get the error below.

      Error creating bean with name ‘org.apache.cxf.jaxws.EndpointImpl–1644645070’: Invocation of init method failed; nested exception is javax.xml.ws.WebServiceException: java.lang.RuntimeException: Port 29488 is configured with wrong protocol “http” for “https://localhost:29488/dummyServerToStartPortForRawServer“

      Does anyone know how to setup and if I need to install/add anything to clover (e.g. certs, licenses)?

      I’m on 6.0 and using CAA-WS

      Thanks,

      Corrie

    • Creator
      Topic
    Viewing 1 reply thread
    • Author
      Replies
      • May 7, 2018 at 6:06 pm #85138
        manoune sadakhom
        Participant

          If you are using Https – this is a secure method therefore it would involved some secure private key files.

          Secondly this sounds like you are intend to use engine as the server mode. It will be more complicated because server would need to have a WSDL file which allow clients that connect to you thru your provided WSDL.

          There are some samples that comes with WSA sites.

        • May 7, 2018 at 7:24 pm #85139
          David Barr
          Participant

            Corrie Henry wrote:

            Error creating bean with name ‘org.apache.cxf.jaxws.EndpointImpl–1644645070’: Invocation of init method failed; nested exception is javax.xml.ws.WebServiceException: java.lang.RuntimeException: Port 29488 is configured with wrong protocol “http” for “https://localhost:29488/dummyServerToStartPortForRawServer”

            This sounds like a problem with your key configuration. If you are using HTTPS then you need to fill in the Keystore/Truststore section of the thread configuration.

        • Author
          Replies
        Viewing 1 reply thread
        • The forum ‘Cloverleaf’ is closed to new topics and replies.