[
https://issues.apache.org/jira/browse/CXF-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565659#comment-15565659
]
ASF GitHub Bot commented on CXF-7084:
-------------------------------------
GitHub user spark404 opened a pull request:
https://github.com/apache/cxf/pull/176
CXF-7084 Add a configurable KeyName value using the properties
I've added properties to EncryptionProperties and SignatureProperties and
also two new SecurityConstants.
This way a KeyName can be directly configured from the *Properties but also
configured per message using a property. The Message configuration has a higher
preference if both are set.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/spark404/cxf CXF-7084
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf/pull/176.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #176
----
commit c297508e7e3b4e69c0824a6faa846ab1e54cd9b1
Author: Hugo Trippaers <[email protected]>
Date: 2016-10-11T14:52:42Z
CXF-7084 Add a configurable KeyName value using the properties
----
> Pass a value for the KeyName element from the XmlSecOutInterceptor to
> Santuario
> -------------------------------------------------------------------------------
>
> Key: CXF-7084
> URL: https://issues.apache.org/jira/browse/CXF-7084
> Project: CXF
> Issue Type: New Feature
> Components: JAX-RS Security
> Reporter: Hugo Trippaers
> Priority: Minor
>
> This relates to issue SANTUARIO-452. The idea is that it is possible to
> configure a value for the KeyName in the properties that will eventually end
> up in the KeyInfo/KeyName field.
> Together with CXF-7080 this provides enough support to handle signing of XML
> documents where the KeyIdentifier needs to be KeyName.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
