Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <1375324403.635801270133727414.JavaMail.jira@brutus.apache.org>
Date: Thu, 1 Apr 2010 14:55:27 +0000 (UTC)
From: "David Valeri (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Updated: (CXF-2639) Expose Cryptographic coverage checking
 code from PolicyBasedWSS4JInInterceptor in a non-WS-Policy based
 interceptor
In-Reply-To: <1212198043.130751264781674650.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

David Valeri updated CXF-2639:
------------------------------

    Fix Version/s: 2.2.8
                   2.3

> Expose Cryptographic coverage checking code from PolicyBasedWSS4JInInterceptor in a non-WS-Policy based interceptor
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2639
>                 URL: https://issues.apache.org/jira/browse/CXF-2639
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>    Affects Versions: 2.3
>            Reporter: David Valeri
>            Assignee: David Valeri
>            Priority: Minor
>             Fix For: 2.3, 2.2.8
>
>
> In some cases, manual configuration of security profile/policy is necessary.  In one particular example, I would like to validate cryptographic coverage of a SOAP message while using a traditionally/manually configured interceptor chain.  The existing code that enforces such coverage is only accessible to PolicyBasedWSS4JInInterceptor and cannot be reused.  Additionally, this code is affected by [CXF-2638].
> The solution could be a class that holds XPath expressions for the different types of required cryptographic coverage and can be injected into a a simple interceptor that is usable without policy based configuration.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.