Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8236645

JDK 8u231 introduces a regression with incompatible handling of XML messages

XMLWordPrintable

        JDK 8u231 introduces a regression with incompatible handling of XML message signing

        Starting with JDK 8u231, there was a change in the way that Oracle Java handles the XML message and signing (possibly related to JDK-8177334 or others).

        The problem breaks existing client systems.

        When a server platform is updated to JDK 8u231, the form of the signed XML messages is changed slightly making them incompatible with older clients already in the field which expect the message to be processed and signed as it was in the past.

        Replacing the clients is a long-term process for end users of customers and is not a workable solution. We need the server and the JDK on the server to provide the same format signed XML messages as they did in the past.

        Possibly the same issue as the regression: JDK-8235603

        This problem is observed while using WebLogic Server 12.1.3.

          1.
          		 Release Note: Oracle Specific JDK Update of System Property to Fall Back to Legacy Base64 Encoding Format Sub-task Closed Kiran Sidhartha Ravikumar (Inactive)  

              kravikumar Kiran Sidhartha Ravikumar (Inactive)
              shadowbug Shadow Bug
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: