UPDATE : I've totally disabled the Distributed Cache, however, the problem is still there.

For the record, I've applied CU7 for AppFabric as well as SharePoint 2013 Server March '13 CU. No luck so far.

One of our team have been deploying a new website using SharePoint API in order to post documents in a dedicated SP2013 Web Application's document library, totally standard one. Their website's web.config points specifically to the url to this web app.

Works well, so far.

However, since they are using this web site fonctionality, posting documents, any user on any other web application may be temporarily logged as the user which has been using this site (Sharepoint logs point me to this).

And that's an issue.

I've been looking around for some information, signs point to - maybe - kerberos and WFE load balancing. For information, Kerberos is fine on all of our webapps, no SPN duplicates or stuff like that. But I'm stuck right now.

Any help would be greatly appreciated.


  • what you saying, you have a web site( non sharepoint) which will upload the documents in the SharePoint site..right? and what is the issue with user?
    – Waqas Sarwar MVP
    Commented Mar 18, 2016 at 12:28
  • The user, let's say "user1", who uploads the document via the external website has no issues. However, the users browsing other web applications hosted on the same farm that the web app where documents are uploaded, may be temporarily logged as "user1". Whatever the web application they are browsing.
    – Jan
    Commented Mar 18, 2016 at 13:22
  • Which SharePoint API are you using? Commented Apr 12, 2016 at 11:05
  • Dunno which code the devs used, but I have a sample : string serverUrl = SharepointService.GetServerUrl(); log.Info("server url : "+serverUrl); using (var clientContext = new SC.ClientContext(serverUrl)) { log.Info("client context initialized"); try { clientContext.Load(clientContext.Web.CurrentUser); clientContext.ExecuteQuery(); }
    – Jan
    Commented Apr 12, 2016 at 12:32
  • That's CSOM. I think the problem may be somewhere in code, not SharePoint configuration. Can you provide us with the code you're using to upload documents? Commented Apr 12, 2016 at 12:49

1 Answer 1


I would like to tell you that we figured out the problem. Some time ago, indeed, and I apologize for not having mentioned the solution here.

The problem was due to our F5 Load Balancer, as an additional configuration was needed. I was able to fix the issue thanks to this article :

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.