Geek asks and answers

Proper WCF Service Authentication in Claims

Claims authenticated SharePoint web applications support NTLM, but only with the following steps:

  • HTTP 302 is redirected to second place.
  • HTTP 401 call for NTLM authorization
  • HTTP Verification 401
  • HTTP 302 redirects back to its original location (service)

Can I write custom behavior, factory channel or binding to handle this? Is there a better way to do this?

+3
source share
1 answer

What you indicated is NTLM standard friction.

One way to avoid this is to use Kerberos instead of NTLM. See: http://technet.microsoft.com/en-us/library/gg502594.aspx

0
source

More articles:


All Articles