ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (WSS-489) Extend Crypto interface with verifyTrustDirect() method
Date Tue, 07 Jan 2014 12:07:52 GMT

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

Colm O hEigeartaigh resolved WSS-489.
-------------------------------------

    Resolution: Fixed

> Extend Crypto interface with verifyTrustDirect() method
> -------------------------------------------------------
>
>                 Key: WSS-489
>                 URL: https://issues.apache.org/jira/browse/WSS-489
>             Project: WSS4J
>          Issue Type: Improvement
>            Reporter: Andrei Shakirin
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.0
>
>         Attachments: crypto-direct-trust.patch
>
>
> Normally validate() operation checks only validity period, trusted chain and CRLs of
X509 certificate. Basically it is not necessary that certificate exists in the repository/keystore.
> However, in some cases it is required that certificate itself is "known" and located
in trusted store or XKMS repository (direct trust).
> To cover this use case I would propose to extend Crypto interface with verifyTrustDirect()
method that cover this functionality. CryptoBase will delegate this method to verifyTrust()
by default.
> See https://issues.apache.org/jira/browse/CXF-5482 for details



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


Mime
View raw message