Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of lawrence.johnbosco@gmail.com
 designates 74.125.46.157 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=cMh7Ib+axk7Pvr/U70sScPEbsW1lC1Icv87M7FfmN1W2pMqOL+e5iUsjxtwpi2Jsn1
         IYHtbn40nFwHzOSOaYqof+AXkWy0avGhrZ9MRsxA0pEd4CYHE/sQcQ867z6ON5Yu7u+p
         AvSl1rAEKTMzvq8ATcUbZUG0FIktIHT6vyTUg=
Message-ID: <c6155b250901081311s4ab28cf8w3d7fadb53d46f044@mail.gmail.com>
Date: Thu, 8 Jan 2009 16:11:04 -0500
From: "Lawrence Johnbosco" <lawrence.johnbosco@gmail.com>
To: users@cxf.apache.org
Subject: Re: WS-Security UsernameToken and WS-Security Encryption together
In-Reply-To: <1231448605.7821.64.camel@pod2132.intware.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_138647_14790843.1231449064969"
References: <c6155b250901081140vdac2cc7wd8957b35dc624cbd@mail.gmail.com>
	 <1231448605.7821.64.camel@pod2132.intware.com>

------=_Part_138647_14790843.1231449064969
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks Steve, I'll give a try.
Lawrence.

On Thu, Jan 8, 2009 at 4:03 PM, Steve Shaw <steve@intelliware.ca> wrote:

>  On Thu, 2009-01-08 at 14:40 -0500, Lawrence Johnbosco wrote:
>
> > Do any of you have a working sample that implements both the WS-Security
> > UsernameToken and WS-Security Encryption together? I'm trying with two
> WSS4J
> > In and Out Interceptors - one for UsernameToken and the other for
> > WS-Security Encryption but ran into issues.
>
> Someone may have a better answer, but I managed to cobble something
> together a few months back. I wrote it up here:
>
> https://i-proving.ca/space/Technologies/Apache+CXF/Provider+Services+and
> +WS-Security
>
> The encryption part is near the bottom of the page.
>
> My posting on this list:
>
> http://www.mail-archive.com/users@cxf.apache.org/msg03037.html
>
> I wasn't especially happy with the result since the changes I made
> rendered the framework incapable of handling other sorts of encryption.
> I need to revisit the code in the near future since it turns out that
> system I'm building is using a non-standard definition of
> UsernameToken's key generation, so I'll have to include my own
> implementation of UsernameToken.
>
> If anyone has a better example, I'd love to see it as I'm sure that my
> code can be improved upon. Your idea of use multiple WSS4J interceptors
> is not something that I considered, and it may prove fruitful.
>
> Finally, there have been several notes about this in the past. I'm not
> sure that anyone has completely solved this problem to their own
> satisfaction.
>
> -Steve
>

------=_Part_138647_14790843.1231449064969--