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

[Ruchith Fernando]

Please set the value of "signatureKeyIdentifier" to "DirectReference".

Thanks,
Ruchith

On 12/11/06, Xinjun Chen <[EMAIL PROTECTED]> wrote:

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

Could anyone enlighten me how to let WSS4J generate what .NET WSE 2.0
expected 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.2
BinarySecurityToken)

<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.1
KeyIdentifier)

<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

--
www.ruchith.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]