Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-1390

Not able to register KIE server if we use https protocol.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 6.2.0
    • 6.1.0
    • Kie-Server
    • None

      Description of problem:
      We are not able to register KIE-server through business central console if we are accessing kie-server over https protocol. We can access kie-server REST API's(https://localhost:8443/kie-server/services/rest/server/)over https through browser but not able to register server.

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:
      1. Create https connector in standalone.xml file by adding following tag in 'web' subsystem
      ~~~
      <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
      <ssl name="https" key-alias="mykey" password="password" certificate-key-file="/path/to/keystore.jks"/>
      </connector>
      ~~~
      2.Start server instance, login into business central console and go to "Deploy"-->"Rule Deployments"
      3.Try to register KIE-server using following URL:
      ~~~
      https://localhost:8443/kie-server/services/rest/server/
      ~~~
      4. It fails with exception "Can't connect to endpoint."

      Actual results:
      Not able to register kie-server over https protocol.

      Expected results:
      Kie-server should be registered successfully over https protocol as well.

      Additional info:

              swiderski.maciej Maciej Swiderski (Inactive)
              rhn-support-abhumbe Abhijit Humbe (Inactive)
              Jakub Schwan Jakub Schwan
              Jakub Schwan Jakub Schwan
              Alessandro Lazarotti, Jakub Schwan, Kris Verlaenen, Maciej Swiderski (Inactive), Marco Rietveld (Inactive), Michael Anstis, Toni Rikkola
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: