You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andreas Vallen (JIRA)" <ji...@apache.org> on 2016/06/23 22:52:16 UTC

[jira] [Created] (CXF-6951) Support using the initiator token's public key for response encryption by recipient

Andreas Vallen created CXF-6951:
-----------------------------------

             Summary: Support using the initiator token's public key for response encryption by recipient
                 Key: CXF-6951
                 URL: https://issues.apache.org/jira/browse/CXF-6951
             Project: CXF
          Issue Type: Improvement
          Components: WS-* Components
    Affects Versions: 3.1.6
            Reporter: Andreas Vallen


Using CXF 3.1.6 and WSS4j 2.1.5, uncommenting some already prepared code unlocked this feature for me :-)

It is two locations in AsymmetricBindingHandler both commented with:

{quote}
TODO when WSS4J 2.1.5 is released
{quote}

Now the encryption username and the crypto configuration may be left unconfigured and encryption will still work properly.

Note that previously it seems that setting the ws-security.encryption.username property to "useReqSigCert" seems to have been the way to achieve the same (as hinted to variously in forums or e.g. in CXF-4274). Looking through the code this however does not seem to be supported anymore for SOAP at least. This has led me down the wrong path for a while. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)