I'm trying to see whether I can preserve some sort of backwards compatibility
for WSE2 before we force people to upgrade to WSE3.  I'm trying to compile
our existing code for configuring the proxy with tokens, but I'm getting the
following error when I call the WebMethod:

   MyNUnitTests.WebServices.TestServiceTests.TestAccessWse :
System.InvalidOperationException : WSE589: Cannot retrieve parent token
reference for a derived key token.

  at
Microsoft.Web.Services3.Security.Tokens.DerivedKeyToken.GetXml(XmlDocument
document)
  at Microsoft.Web.Services3.Security.Security.SerializeXml(SoapEnvelope
document)
  at
Microsoft.Web.Services3.Security.SecurityOutputFilter.ProcessHeader(Security
security, SoapEnvelope envelope)
  at
Microsoft.Web.Services3.Security.SecurityOutputFilter.ProcessMessage(SoapEnvelope envelope)
  at
Microsoft.Web.Services3.Security.Wse2PipelinePolicy.LegacyFilterWrapper.ProcessMessage(SoapEnvelope envelope)
  at Microsoft.Web.Services3.Pipeline.ProcessOutputMessage(SoapEnvelope
envelope)
  at Microsoft.Web.Services3.Xml.SoapEnvelopeWriter.Finish()
  at Microsoft.Web.Services3.Xml.XmlWrappingWriter.Flush()
  at
System.Web.Services.Protocols.SoapHttpClientProtocol.Serialize(SoapClientMessage message)
  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)

I can't find any reference to this error anywhere.  The code which I use to
configure the proxy is:

           DerivedKeyToken dk1 = new DerivedKeyToken(token);

           proxy.RequestSoapContext.Security.Tokens.Add(dk1);

           // Sign the Message
           proxy.RequestSoapContext.Security.Elements.Add(
               new MessageSignature(dk1));

           // Encrypt the Message
           proxy.RequestSoapContext.Security.Elements.Add(
               new EncryptedData(dk1));

Thanks,

-Mike