EncryptedKey in WSE 2.0 -> "Referenced security token could not be retrieved"

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Franco via .NET 247 (anonymous_at_dotnet247.com)
Date: 08/11/04


Date: Wed, 11 Aug 2004 13:54:33 -0700

I wrote a .net client using WSE 2.0 to talk to a web service.
The client signs the request.
The response signs the response.
So far so good.

However, i extended the service to encrypt the response. The symmetric key used to encrypt the reponse is itself encrypted using the client's x509 cert embedded in the request (in a typical EncryptedKey element).

The WSE client can't seem to handle this EncryptedKey element. It throws the following exception:

Microsoft.Web.Services2.Security.SecurityFault: Referenced security token could
not be retrieved
   at Microsoft.Web.Services2.Security.EncryptedKey.LoadXml(XmlElement element)
   at Microsoft.Web.Services2.Security.EncryptedKey..ctor(XmlElement element)
   at Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement element)
   at Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage
(SoapEnvelope envelope)
   at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope
envelope)

--------------------------------
From: Francois Lascelles

-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)

<Id>gUaY272TeU67xK8etYqdWQ==</Id>



Relevant Pages

  • Re: WSE 3.0 + UserNameToken without X.509 Cert/Kerberos + Signing + Encryption How?
    ... I still think that there is a lot of benefit for Secure Conversation ... message security and thefore it does not encrypt the message. ... between client and server using a UserNameToken that passes the UserName ... assuming the client request adds a proper UserNameToken... ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Encrypting the response
    ... encrypt the response with the token that was used to sign the request. ... You should encrypt the response with the token that was used to encrypt the ... encrypting tokens in separate functions. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: New to Java - Guidance Required
    ... All of these do essentially the same thing, communicate a request from the client to a service asking it to do something for you. ... I'm currently working on a project where I need a client to be able to send a request and get a response. ... In yet another instance I needed to have a continuous two way dialogue between an applet and the server from which it came - in this particular case I had to use sockets. ...
    (comp.lang.java)
  • Re: How to remove HTTP Header [Expect: 100-continue]
    ... RESPONSE to redirect, then client makes another requests and gets a 200 Ok. ... > CLIENT:: Request ... The Java Client Header look ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Response blockieren
    ... Ein Client sendet einen Request an den Webserver. ... Danach sendet der Linuxrechner eine Nachricht an den Windows-Sever. ... Und jetzt würde ich gerne die Webseite-Klasse informieren, dass der Response ...
    (microsoft.public.de.german.entwickler.dotnet.asp)