You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "David Valeri (JIRA)" <ji...@apache.org> on 2010/03/23 02:25:27 UTC

[jira] Assigned: (CXF-2639) Expose Cryptographic coverage checking code from PolicyBasedWSS4JInInterceptor in a non-WS-Policy based interceptor

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

David Valeri reassigned CXF-2639:
---------------------------------

    Assignee: David Valeri

> 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
>
> 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.