[jira] [Created] (WSS-625) Use RFC4648 base64 encoder for signature values and BST

Tue, 27 Feb 2018 23:49:20 -0800 

Willem Salembier created WSS-625:
------------------------------------

             Summary: Use RFC4648 base64 encoder for signature values and BST
                 Key: WSS-625
                 URL: https://issues.apache.org/jira/browse/WSS-625
             Project: WSS4J
          Issue Type: Bug
          Components: WSS4J Core
    Affects Versions: 2.2.1
            Reporter: Willem Salembier
            Assignee: Colm O hEigeartaigh


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

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


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

Perhaps make it configurable

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to