[RAMPART-277] Rampart ignores token inclusion settings when using the asymmetric security binding

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5
• Fix Version/s: 1.5.1
• Component/s: rampart-core
• Assignee: Selvaratnam Uthaiyashankar
• Reporter: Dave Bryant
• Created: 13/Jan/10 02:02
• Updated: 22/Dec/10 07:08
• Resolved: 22/Dec/10 07:08

Description

Consider the abbhreviated policy below. It defines x509 tokens for the initiator and recipient: the initiator's token must be included in all messages from the initiator to the recepient, and the recipient's token must not be included at all.

<wsp:Policy wsu:Id="servicePolicy">
  <sp:AsymmetricBinding>
    <sp:InitiatorToken>
      <sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient"/>
    </sp:InitiatorToken>
    <sp:RecipientToken>
      <sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never"/>
    </sp:RecipientToken>
</wsp:Policy>

When Rampart is used as both the client and server for a web service using this policy, the client's certificate is correctly included as a binary security token in the request. However, the response message from the server to the client also includes this as a binary security token when reference which token was used to encrypt the encrypted symmetric key. This is incorrect as the token was marked as only to be included in messages from the initiator to the recipient.

The problem is that the asymmetric security binding uses RampartUtil.setKeyIdentifierType() to determine what type of key references should be used. As present it will always include a binary security token unless the token inclusion parameter is set to never - i.e. it does not take into account whether we are the initiator or not, and so doesn't handle the alwaysToInitiator and alwaysToRecipient inclusion modes.