You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2009/12/04 20:35:20 UTC

[jira] Resolved: (CXF-2553) WS-Security UsernameToken sample using WS-SecurityPolicy

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

Daniel Kulp resolved CXF-2553.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.6
         Assignee: Daniel Kulp


Thanks!

Just had to fix a single checkstyle error and a line break in the readme.   Thanks a bunch!

> WS-Security UsernameToken sample using WS-SecurityPolicy
> --------------------------------------------------------
>
>                 Key: CXF-2553
>                 URL: https://issues.apache.org/jira/browse/CXF-2553
>             Project: CXF
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Oliver Wulff
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: 2.2.6
>
>         Attachments: ut_policy.zip
>
>
> I'd like to submit this demo which combines https and usernametoken based on WS-SecurityPolicy configuration.
> The attached demo is an extension of the ws-sec demo ut. I took the demo wsdl_first_https as the base for https and configured UsernameToken enforcement with WS-SecurityPolicy.
> We configure the CXF version like this:
>     <properties>
>         <cxf.version>[2,)</cxf.version>
>     </properties>
> Is this really intended that when I download CXF 2.2.4 and run the demo with maven, the more recent CXF version (2.2.5) is used?

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