StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Well, with your current client setup, you are expecting to encrypt and sign your messages and send along your Windows credentials as identity.</p> <p>If the remote server which attempts to handle this request is <strong>NOT</strong> on the same LAN or doesn't have access to the same Active Directory to validate these user credentials, you'll get this message.</p> <p>The security settings on the server and the client have to match - e.g. if your server has something like </p> <pre><code><security mode="None"> </code></pre> <p>then you have to have the same settings on the client as well. If your server cannot validate the Windows credentials, then don't use them. Either use no security at all (not advisable! except for development/testing), or allow anonymous callers (but still use e.g. message security), or then you have to define a custom mechanism in which the caller can authenticate itself.</p> <p>Security in WCF is a vast field :-) Here's some links that might help get a grip on the topic:</p> <ul> <li><a href="http://blogs.microsoft.co.il/blogs/davids/archive/2009/06/11/wcf-security-scenarios-read-out-loud.aspx" rel="nofollow noreferrer">WCF SEcurity Scenarios</a> based on Juval Lowy's excellent "Programming WCF" book</li> <li><a href="http://msdn.microsoft.com/en-us/magazine/cc163382.aspx" rel="nofollow noreferrer">Juval Lowy's Declarate WCF Security</a> article on how to handle security with just a few attributes</li> </ul> <p>and for a really complete, but also almost daunting overview of all things security related in WCF, there's the <a href="http://www.codeplex.com/WCFSecurity/" rel="nofollow noreferrer">WCF Security Guidance</a> on CodePlex.</p> <p>Hope this helps get you started!</p> <p>Marc</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload