[WSS-222] SignatureProcessor does not provide correct signature coverage results with STR Dereference Transform

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.8
• Fix Version/s: 1.5.9, 1.6
• Component/s: WSS4J Core
• Assignee: Colm O hEigeartaigh
• Reporter: David Valeri
• Created: 15/Jan/10 20:50
• Updated: 27/Jul/10 18:21
• Resolved: 17/May/10 14:27

Description

SignatureProcessor does not report correct info when STR Dereference Transform is used. The implementation does not follow the dereference pointer to the security token and reports that the signed content is the SecurityTokenReference itself and not the referenced token. The URI in the signature part is dereferenced with no regard to the transform used in the signature part.

This issue makes it difficult to validate signature coverage over something like an embedded SAML assertion when that assertion is also used as the key material for the signature and is referenced and signed through a SecurityTokenReference.

Issue Links

• blocks: CXF-2913 Cannot detect signature coverage of SOAP elements referenced through the Security Token Reference Dereference Transform