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 2019/10/16 16:00:00 UTC
[jira] [Resolved] (WSS-656) Add the ability to specify a security
Provider to use with Signature
[ https://issues.apache.org/jira/browse/WSS-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-656.
-------------------------------------
Resolution: Fixed
> Add the ability to specify a security Provider to use with Signature
> --------------------------------------------------------------------
>
> Key: WSS-656
> URL: https://issues.apache.org/jira/browse/WSS-656
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Priority: Major
> Fix For: 2.3.0, 2.2.5
>
>
> It's possible to set a security Provider to use with Signature via the JSR-105 API, by setting the "org.jcp.xml.dsig.internal.dom.SignatureProvider" property to the Provider in the DOMSignContext.setProperty method (ref: https://issues.apache.org/jira/browse/SANTUARIO-509).
> This task is to add support to WSSEcSignature, and SignatureProcessor to set this property if a security provider is specified. A new method "setSignatureProvider" is added to WSSecSignature if working directly with the API. On the receiving side, it can be set via RequestData.setSignatureProvider().
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org