You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/10/11 16:48:20 UTC

[jira] [Commented] (SANTUARIO-453) Support selection of a signature validation certificate based on KeyName

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

ASF GitHub Bot commented on SANTUARIO-453:
------------------------------------------

GitHub user spark404 opened a pull request:

    https://github.com/apache/santuario-java/pull/8

    SANTUARIO-453 Use a map in the properties to select the signature cert

    Looking for feedback if this is the right way to do this

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/spark404/santuario-java SANTUARIO-453

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/santuario-java/pull/8.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 #8
    
----
commit e08de2d7e791c011344ed2f57d9f2f2137288258
Author: Hugo Trippaers <ht...@schubergphilis.com>
Date:   2016-10-11T16:39:15Z

    SANTUARIO-453 Use a map in the properties to select the signature validation certificate for a KeyName

----


> Support selection of a signature validation certificate based on KeyName
> ------------------------------------------------------------------------
>
>                 Key: SANTUARIO-453
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-453
>             Project: Santuario
>          Issue Type: New Feature
>          Components: Java
>            Reporter: Hugo Trippaers
>            Assignee: Colm O hEigeartaigh
>
> The signature trust is currently done based on a preconfigured SignatureValidationKey. However when KeyName is used it is possible to have multiple messages with different KeyNames. The inbound processing should be able to deal with this and select the right certificate to use when validating a message.



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