Does WSS4J implement WS-Security 1.0 X509Certificate Token Profile 3.3.2 BinarySecurityToken

[Xinjun Chen]

Does WSS4J implement WS-Security 1.0 X509 Certificate Token Profile
3.3.2BinarySecurityToken?

Could anyone enlighten me how to let WSS4J generate what .NET WSE
2.0expected security headers (<KeyInfo>)?
Or in another way, how can I modify .NET WSE 2.0 configuration so that .NET
WSE 2.0 accepts what WSS4J generated security headers(<KeyInfo>)?

.NET expects: (WS-Security 1.0 X509 Certificate Token Profile
3.3.2BinarySecurityToken)

<wsse:Security>
<*wsse:BinarySecurityToken>theWholeCertificate</wsse:BinarySecurityToken*>
<Signature>
...
 <KeyInfo>
  <wsse:SecurityTokenReference>
   <*wsse:Reference*>
  </wsse:SecurityTokenReference>
 </KeyInfo>
</Signature>
</wsse:Security>
But WSS4J generates: (WS-Security 1.0 X509 Certificate Token Profile
3.3.1KeyIdentifier)

<wsse:Security>
<Signature>
...
 <KeyInfo>
  <wsse:SecurityTokenReference>
   <*wsse:KeyIdentifier>theWholeCertificate</wsse:KeyIdentifier*>
  </wsse:SecurityTokenReference>
 </KeyInfo>
</Signature>
</wsse:Security>

How can I ask WSS4J to generate what .NET expected?

Regards,
Xinjun