All -
We continue to have a problem with a simple signed response using WSE
2.0.
We keep getting the following error message:
"The signature or decryption was invalid"
Our client is .Net using WSE 2.0. The Service is a WebLogic web
service.
I'm using a Cert generated by our Cert Authority to generate a Client
Authentication Certificate, Microsoft Base Crypto v1.0, Key Usage
Both, Hash Algorithm SHA-1.
The request gets processed properly by the server, but the response
keeps failing with the above message.
What should I look at next and / or change? I have a feeling it's how
I'm creating the cert, but I'm not sure.
Thanks,
- Matt Sajdera
- msajdera@ncen.com
Lucien - 27 Jul 2004 20:26 GMT
Does the response contain a signature or decryption? If it does can you post
piece of these security headers?
> All -
>
[quoted text clipped - 20 lines]
> - Matt Sajdera
> - msajdera@ncen.com
Byron Kim - 27 Jul 2004 21:12 GMT
I suspect client receives x509 signed message but the STR has KeyName which
is not supported by WSE by default.
<xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-_5">
- <dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<dsig:KeyName>CN=WSE2QuickStartClient</dsig:KeyName>
</dsig:KeyInfo>
- <xenc:CipherData>
So, you need to override
X509SecurityTokenManager.LoadTokenFromKeyInfo(KeyInfo keyInfo)
And return X509token for signature verification
Byron KIM
> All -
>
[quoted text clipped - 20 lines]
> - Matt Sajdera
> - msajdera@ncen.com
Byron Kim - 27 Jul 2004 21:37 GMT
Please note that this is not compilant with X509 profile and WS-I BSP. That
is the reason why WSE does not support this by default.
bckim
> I suspect client receives x509 signed message but the STR has KeyName which
> is not supported by WSE by default.
[quoted text clipped - 42 lines]
> > - Matt Sajdera
> > - msajdera@ncen.com