7 Replies Latest reply on Jun 6, 2016 7:51 AM by Rustam Usmanov

    Secure JBPM Application

    Abhishek Mittal Novice

      Hello,

       

      By default, jBPM runs with TCP 8080 HTTP request.

       

      If I want to secure it using TCP 443 HTTPS request, please let me know the procedure to do the same.

       

       

      Regards,

      Abhishek

        • 2. Re: Secure JBPM Application
          Abhishek Mittal Novice

          Hi Rustam,

           

          Please let me know where do I need to mention these settings/which file/folder in Wildfly server.

           

           

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

           

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

           

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

              <ssl name="foo-ssl" password="secret" certificate-key-file="../standalone/configuration/foo.pem" certificate-file="../standalone/configuration/foo-cert.pem"/>

            </connector>

           

          -Abhishek

          • 3. Re: Secure JBPM Application
            Rustam Usmanov Apprentice

            You need to apply the settings to WilfFly configuration file.

            • 4. Re: Secure JBPM Application
              Abhishek Mittal Novice

              Do I need to add these mappings in this file 'standalone.xml'?

              • 5. Re: Secure JBPM Application
                Rustam Usmanov Apprentice

                May be. It depends on which configuration file you actually use. It could be standalone-full.xml.

                • 6. Re: Secure JBPM Application
                  Abhishek Mittal Novice

                  Hello,

                   

                  I have created 2 certificates and added them to /configuration folder and provide their references in standalone-full.xml as below. I am getting the below exception.

                  Please suggest.

                   

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

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

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

                    <ssl name="foo-ssl" password="secret" certificate-key-file="../standalone/configuration/cakey.pem" certificate-file="../standalone/configuration/cacert.pem"/>

                    </connector>

                    </subsystem>

                   

                  Exception:

                  org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration

                    at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.2.1.Final.jar:8.2.1.Final]

                    at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.2.1.Final.jar:8.2.1.Final]

                    at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:259) [wildfly-controller-8.2.1.Final.jar:8.2.1.Final]

                    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]

                  Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[454,99]

                  Message: Unexpected element '{urn:jboss:domain:web:1.1}subsystem'

                    at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) [staxmapper-1.1.0.Final.jar:1.1.0.Final]

                    at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]

                    at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1131) [wildfly-server-8.2.1.Final.jar:8.2.1.Final]

                    at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:458) [wildfly-server-8.2.1.Final.jar:8.2.1.Final]

                    at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [wildfly-server-8.2.1.Final.jar:8.2.1.Final]

                    at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.2.1.Final.jar:8.2.1.Final]

                    at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]

                    at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]

                    at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.2.1.Final.jar:8.2.1.Final]

                   

                  Attaching the configuration file for reference.

                  • 7. Re: Secure JBPM Application
                    Rustam Usmanov Apprentice

                    Obviously your standalone-full.xml is invalid:

                    xmllint standalone-full.xml

                    standalone-full.xml:462: parser error : Opening and ending tag mismatch: subsystem line 453 and profile

                        </profile>

                                  ^

                    standalone-full.xml:494: parser error : Opening and ending tag mismatch: profile line 81 and server

                    standalone-full.xml:494: parser error : Premature end of data in tag server line 3