[RAMPART-115] Incrorrect reference URI in the soap response in Secure Conversation Scenarios

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4
• Component/s: rampart-core
• Assignee: Nandana Mihindukulasooriya
• Reporter: Nandana Mihindukulasooriya
• Created: 22/Nov/07 04:25
• Updated: 27/May/08 05:12
• Resolved: 14/Dec/07 13:44

Description

Currently generated reference URI in the signature element is something like

<ds:KeyInfo Id="KeyId-23512756">
<wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="STRId-8347238">
<wsse:Reference URI="#urn:uuid:7C508C42E7E4A7A229119570507177149" ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0#SAMLAssertionID" />
</wsse:SecurityTokenReference>
</ds:KeyInfo>

where it should be something like,

<ds:KeyInfo Id="KeyId-23512756">
<wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="STRId-8347238">
<wsse:Reference URI="#sctId-23510169" ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0#SAMLAssertionID" />
</wsse:SecurityTokenReference>
</ds:KeyInfo>

This happens because when SimpleTokenStore finds the token using attached reference or unattached reference, the returned token's id is not the same id
we entered to retrieve the token. So the incorrect value is used in reference URI.