You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2018/02/28 09:43:00 UTC
[jira] [Commented] (WSS-625) Use RFC4648 base64 encoder for
signature values and BST
[ https://issues.apache.org/jira/browse/WSS-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380059#comment-16380059 ]
Colm O hEigeartaigh commented on WSS-625:
-----------------------------------------
The spec says that RFC-2045 should be used:
"The {{SignatureValue}} element contains the actual value of the digital signature; it is always encoded using base64 [??[RFC2045|https://www.w3.org/TR/xmldsig-core1/#bib-RFC2045]??]. "
I'll add a configuration switch though, as a few people have requested it.
> 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
> Priority: Major
>
> The upgrade to JDK 8 Base64 RFC2045 mime encoder breaks our clients because all CR gets escaped to {{& #13;}}.
> {code}<ds:SignatureValue>ZizIuoDNc7Sn9wnvP6HC0NlouooLq2UdjOHcvGDkDPLjXnJgoVRgO5PTEfLJlNQErF6PWiMwL48d
> 2yCW5eop7aVHgSdL7o744Y4tb3nbQC48F8SIn64IR2XQsisF8wnpaz8krjOQWOFOzyznh3/xVyul
> lxiVVx0bTiIMWM9aQ4HKNUbLVfPxZxrQcbtduOioKzYfydJzEek3Z4/8GGMGERlYb5Wy/RHjzHkX
> TUz7l0Vg0bATDN3/lBwrwB1Aiu/79e+eURj5BFIwvveW/hjC1zcq2PqWzsx+2KP4zh+FIqtyk703
> 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: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org