Blogger :
hongmeigs WebLog
All posts :
All posts by hongmeigs WebLog
Category :
WSCF/WCF
Blogged date : 2006 Dec 06
If you are getting error from the client saying certain token provider is not registered to deserialize the token, and if you are happening to be using this security binding:
SecurityBindingElement element = SecurityBindingElement.CreateMutualCertificateBindingElement(MessageSecurityVersion.WSSecurity10WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10);
Then a very likely reason is that your server has included the x509 certificate in the response. The following flag is going to allow this scenario:
((AsymmetricSecurityBindingElement)element).AllowSerializedSigningTokenOnReply = true;
If the client already has the server's certificate, it typically won't expect it in the response. That is why by default, WCF client is not expecting the server cert in the response.
Contents
ReBlogger Contents
Email TopXML