Hi Stephen, I tested on WSS4J trunk + signing an Assertion using a signature parts similar to what you specified works:
http://svn.apache.org/viewvc?view=revision&revision=r1640900 Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com On Wed, Nov 19, 2014 at 9:31 PM, <[email protected]> wrote: > In some of my legacy WSS4J 1.5/CXF 2.7 code, I was able to add > “Assertion” to the signatureParts of the WSS4J out interceptor to include > the Assertion as a signed supporting token. But now, using WSS4J 1.6 / CXF > 2.7, that doesn’t work. When I try adding “Assertion”, I get an exception > stating that the signature can’t be created because “Assertion” can’t be > found. I get the same when I try adding it as > “{Element}{urn:oasis:names:tc:SAML:1.0:assertion}Assertion”. Can someone > kick me in the right direction for this? > > > > Thanx, > > > > *Stephen W. Chappell* > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
