[
https://issues.apache.org/jira/browse/WSS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Berger updated WSS-698:
------------------------------
Summary: No way to call requestData.setSignatureProvider() in
WSS4JOutInterceptor and ValidateAssertionInterceptor (was: No way to call
requestData.setSignatureProvider() in WSS4JOutInterceptor)
> No way to call requestData.setSignatureProvider() in WSS4JOutInterceptor and
> ValidateAssertionInterceptor
> ---------------------------------------------------------------------------------------------------------
>
> 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.
> Users should be able to influence the behavior via
> 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: [email protected]
For additional commands, e-mail: [email protected]
