Can I avoid client authentication when using secure TCP channel?
I would like to use a "secure" TCP remoting channel to ensure that my data
is encrypted. I have my own authentication mechanism since clients will
normally not be members of the server's domain.
From reading newsgroup posts, it appears that when using a secure TCP
channel, the server's operating system will always try to authenticate the
client's credentials. Is this true?! It seems to be true since (before
control gets to my server object) I get "The server has rejected the client
credentials." whenever I test from non-domain client machines. Testing from
client machines logged into the domain works fine.
I don't want Windows to try to authenticate the client. I simply want
encryption. Am I out of luck?
Date:Wed, 22 Aug 2007 14:34:21 -0600
Author:
|