[
https://issues.apache.org/jira/browse/WSS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved WSS-698.
-------------------------------------
Resolution: Not A Problem
You have the option of overriding the WSHandler doSenderAction/doReceiverAction
methods, by subclassing WSS4JOut/InInterceptor. Otherwise, please submit a PR
to CXF to add support to manually configure the signature provider via
configuration.
> No way to call requestData.setSignatureProvider() in WSS4JOutInterceptor and
> WSS4JInInterceptor
> -----------------------------------------------------------------------------------------------
>
> Key: WSS-698
> URL: https://issues.apache.org/jira/browse/WSS-698
> Project: WSS4J
> Issue Type: Bug
> Reporter: Stefan Berger
> Assignee: Colm O hEigeartaigh
> Priority: Major
>
> In WSS-656, the ability to set the signatureProvider was added, but when
> using the WSS4JOutInterceptor, the RequestData object is created inside of
> handleMessageInternal() and cannot be modified from the outside.
> WSS4JInInterceptor.handleMessageInternal() behaves similarly.
> Users should be able to influence the behavior via the SoapMessage. (Either
> in the SoapMessage or in the Exchange)
> My use case is that I want to sign with brainpoolP256r1 Certificates in Java
> 17. Oracle removed brainpool support in JDK 15, so now I have to use
> BouncyCastle to sign requests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org
For additional commands, e-mail: dev-h...@ws.apache.org
