Uploaded image for project: 'WSS4J'
  1. WSS4J
  2. WSS-625

Use RFC4648 base64 encoder for signature values and BST

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 2.2.2
    • Component/s: WSS4J Core
    • Labels:
      None

      Description

      The upgrade to JDK 8 Base64 RFC2045 mime encoder breaks our clients because all CR gets escaped to & #13;.

      <ds:SignatureValue>ZizIuoDNc7Sn9wnvP6HC0NlouooLq2UdjOHcvGDkDPLjXnJgoVRgO5PTEfLJlNQErF6PWiMwL48d&#13;
      2yCW5eop7aVHgSdL7o744Y4tb3nbQC48F8SIn64IR2XQsisF8wnpaz8krjOQWOFOzyznh3/xVyul&#13;
      lxiVVx0bTiIMWM9aQ4HKNUbLVfPxZxrQcbtduOioKzYfydJzEek3Z4/8GGMGERlYb5Wy/RHjzHkX&#13;
      TUz7l0Vg0bATDN3/lBwrwB1Aiu/79e+eURj5BFIwvveW/hjC1zcq2PqWzsx+2KP4zh+FIqtyk703&#13;
      PM/ahJpntuRoVR+dvDrfEKbMQK0TNswJoWtUjg==</ds:SignatureValue>
      

      Can the behavior from version 2.1.12 be kept. Instead of Base64.getMimeEncoder() use Base64.getEncoder()

      Perhaps make it configurable

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                coheigea Colm O hEigeartaigh
                Reporter:
                wsalembi Willem Salembier
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: