Hi Freddy, It was a regression in WSS4J. I've just merged a fix.
Thanks, Colm. On Mon, Dec 2, 2013 at 9:55 PM, Freddy Exposito <[email protected]> wrote: > Hi Colm, > > After the svn WSS4J revision 1412163, the method > SAMLTokenProcessor.handleSAMLToken() started calling > SAMLUtil.getCredentialDirectlyFromKeyInfo() instead of > SAMLUtil.getCredentialFromKeyInfo() and the error that DTaylor mentioned > before (SecurityTokenReference not being parsed inside KeyInfo) is > appearing > again for us (DTaylor and I work in the same team). > > Is this a bug in WSS4J? Was the parsing of SecurityTokenReference inside > KeyInfo explicitly deleted or have we misconfigured something? > > Thanks, > Freddy > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Issue-with-SecurityReferenceToken-handling-tp5709621p5737288.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
