You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2017/03/29 09:25:41 UTC

[jira] [Commented] (CXF-7086) Dynamically load signature validation keys using KeyName

    [ https://issues.apache.org/jira/browse/CXF-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946799#comment-15946799 ] 

Colm O hEigeartaigh commented on CXF-7086:
------------------------------------------

Patch applied with some modifications + a test added. I moved the signature key name alias map from SecurityConstants to SignatureProperties.

> Dynamically load signature validation keys using KeyName
> --------------------------------------------------------
>
>                 Key: CXF-7086
>                 URL: https://issues.apache.org/jira/browse/CXF-7086
>             Project: CXF
>          Issue Type: New Feature
>          Components: JAX-RS Security
>            Reporter: Hugo Trippaers
>            Assignee: Colm O hEigeartaigh
>            Priority: Minor
>             Fix For: 3.1.11, 3.2.0
>
>
> The current implementation of handling incoming messages with a KeyName identifier is to rely on a single "default" key. The SignatureValidationKey. However it is possible to have multiple different KeyNames and the expected behaviour is to select the right certificate based on the KeyName.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)