Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-15576

(7.2.z) Uploading content from HAL in SSL doesn't work

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.2.0.GA
    • 7.1.4.GA
    • Undertow, Web Console
    • None
    • Hide
      • Requires management secured using legacy two-way SSL:
        • /core-service=management/security-realm=ManagementRealm/server-identity=ssl:add(keystore-path=windows2008-1.gsslab.rdu2.redhat.com.jks, keystore-relative-to=jboss.server.config.dir, keystore-password="12345678", alias="windows2008-1.gsslab.rdu2.redhat.com")
        • /core-service=management/security-realm=ManagementRealm/authentication=truststore:add(keystore-path=truststore.jks, keystore-relative-to=jboss.server.config.dir, keystore-password="12345678")
        • /core-service=management/management-interface=http-interface:write-attribute(name=secure-socket-binding, value=management-https)
        • /core-service=management/management-interface=http-interface:undefine-attribute(name=socket-binding)
        • reload
      • Then try to deploy war file using web console
      Show
      Requires management secured using legacy two-way SSL: /core-service=management/security-realm=ManagementRealm/server-identity=ssl:add(keystore-path=windows2008-1.gsslab.rdu2.redhat.com.jks, keystore-relative-to=jboss.server.config.dir, keystore-password="12345678", alias="windows2008-1.gsslab.rdu2.redhat.com") /core-service=management/security-realm=ManagementRealm/authentication=truststore:add(keystore-path=truststore.jks, keystore-relative-to=jboss.server.config.dir, keystore-password="12345678") /core-service=management/management-interface=http-interface:write-attribute(name=secure-socket-binding, value=management-https) /core-service=management/management-interface=http-interface:undefine-attribute(name=socket-binding) reload Then try to deploy war file using web console

    Description

      When uploading a file from the web console to WildFly using an SSL secured connection the content is not stored, it is replaced by the Base64 DMR operation.
      Looking at the request I didn't see the file part of the multipart request the parsing return only 1 part while the request on management-upload seems to have 2 parts (see attached har file).
      It doesn't happen with the jboss-cli (ssl or not) nor in HAL on HTTP.

      NOTE:
      For attachments see linked upstream Jira WFLY-11089

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4149 Uploading content in SSL doesn't work

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15548 [GSS](7.1.z) Uploading content from HAL in SSL doesn't work

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15949 [GSS](7.2.z) deployment files upload are corrupted when management console is configured for access with HTTPS

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-15688 Undertow 2.0.14.Final

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15954 (7.2.z) Test case for WFCORE-4149

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          links to

          Web Link KCS#3630381

          Activity

            People

              thofman Tomas Hofman
              thofman Tomas Hofman
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: