[RAMPART-411] Unable to sign the BinarySecurityToken using Rampart 1.6.2

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 1.6.2
• Component/s: rampart-policy
• Environment: Axis2 1.6.2 , Java 7 and Rampart 1.6.2
• Assignee: Unassigned
• Reporter: Ashok T
• Created: 25/Feb/14 12:24
• Updated: 25/Feb/14 12:24

Description

While try to enable the binarysecuritytoken in the signatureparts in the axis2.xml am getting this error . This is happpened only when adding BST element

axis2.xml
----------

<action>
<items>Timestamp Signature</items>
<user>Test User</user>
<passwordCallbackClass>com.PWCBHandler</passwordCallbackClass>
<signaturePropFile>client.properties</signaturePropFile>
<signatureParts>

{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Timestamp;
{Element} {http://schemas.xmlsoap.org/soap/envelope/}

Body;

{Element} {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}

BinarySecurityToken
</signatureParts>
<signatureKeyIdentifier>DirectReference</signatureKeyIdentifier>
</action

org.apache.ws.security.WSSecurityException: General security error (WSEncryptBody/WSSignEnvelope: Element to encrypt/sign not found: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd, BinarySecurityToken)
at org.apache.ws.security.message.WSSecSignatureBase.addReferencesToSign(WSSecSignatureBase.java:160)