[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlrpc-dev
Subject:    [jira] [Closed] (WSS-656) Add the ability to specify a security Provider to use with Signature
From:       "Colm O hEigeartaigh (Jira)" <jira () apache ! org>
Date:       2020-03-18 7:18:00
Message-ID: JIRA.13262662.1571241410000.84349.1584515880412 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/WSS-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Colm O hEigeartaigh closed WSS-656.
-----------------------------------

> 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


[prev in list] [next in list] [prev in thread] [next in thread]