0

My administration page and webpart make calls to a service via .Net remoting.

I've added AD credential checking to the service and discovered that the calls being made from both the admin page and the web part are coming thru as "NT AUTHORITY\ANONYMOUS LOGON" instead of the logged-on user.

As a test, I've written a WinForms application that makes the same calls and the service is correctly figuring out the credentials.

So....is there some special code that I can add to my SharePoint code to get the correct username attached to the thread making the calls?

Improve this question

1 Answer 1

Reset to default
2

I assume the service is running on a seperate server? It sounds like uou are running into the classic "double hop" issue with authentication.

Here is one (of many) blog posts that describes the double-hop authentication issue.

Double-hop authentication: Why NTLM fails and Kerberos works

You have 3 choices:

  • Configure Kerberos (doable)
  • Configure Claims and re-instrument your .NET remoting service to support claims (complicated)
  • Use the Secure Store Service and configure single sign-on
Improve this answer
1
  • Thanks Chris, I had COMPLETELY forgotten about the double-hop problem. I ran the service on the SharePoint server and the problem went away.
    – Iunknown
    Commented Apr 14, 2011 at 1:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.