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

List:       ws-general
Subject:    [jira] [Created] (WSS-698) No way to call requestData.setSignatureProvider() in WSS4JOutInterceptor
From:       "Stefan Berger (Jira)" <jira () apache ! org>
Date:       2022-09-12 19:08:00
Message-ID: JIRA.13481169.1663009672000.288632.1663009680011 () Atlassian ! JIRA
[Download RAW message or body]

Stefan Berger created WSS-698:
---------------------------------

             Summary: No way to call requestData.setSignatureProvider() in \
WSS4JOutInterceptor  Key: WSS-698
                 URL: https://issues.apache.org/jira/browse/WSS-698
             Project: WSS4J
          Issue Type: Bug
            Reporter: Stefan Berger
            Assignee: Colm O hEigeartaigh


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 set a ConfigurationConstant in the SoapMessage to trigger the \
Setter.

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-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]