cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CXF-6951) Support using the initiator token's public key for response encryption by recipient
Date Fri, 24 Jun 2016 11:49:16 GMT

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

Colm O hEigeartaigh reassigned CXF-6951:
----------------------------------------

    Assignee: Colm O hEigeartaigh

> 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
>            Assignee: Colm O hEigeartaigh
>              Labels: easyfix, features, security
>             Fix For: 3.1.7
>
>
> 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)

Mime
View raw message