SPContext.Current.Web.CurrentUser returns wrong user

Question

This is a repeat of a similar question which was never answered so I wanted to give it a fresh start. In fact it looks like some SPDoctor closed it with very odd comments.

Anyway; I have a web part that does nothing other than retrieves the current user and formats a nice welcome message.

 string currentWeb = "", fullName = "";

        try
        {
            fullName = SPContext.Current.Web.CurrentUser.Name.ToString();
            currentWeb = SPContext.Current.Web.Title.ToString();
        }
        catch
        {
            fullName = "Guest";
            currentWeb = "St. Joseph";
        }

        ltfullName.Text = "<h2>" + fullName + ",</h2>";
        ltsiteName.Text = "<h3>" + currentWeb + "</h3>";

I too am having intermittent users report that it is not their name but some other user.

We are thinking that either this is some type of Netscaler / load balancer setting causing this or some type of bug in the MS API?

Answer 1

This has happened to me when I used caching. I wrongly configured the output cache causing SharePoint to return pages already rendered by other users. Therefore showing the name on the webpart of another user. So maybe check on that.

Another one could be to check your loadbalancer to have sticky sessions (affinity) configured. If it has affinity on users should always land on the same Web Front End.

Answer 2

Does it starts giving wront output from the first request itself, or it starts failing in subsequent requests?

Do you have other web parts on the page that might be conflicting with this web part.

I have never had any issues using this method call, do you think you have impersonation enabled in some other part of the code?

Answer 3

I've came across something similar, quite a few years ago though. The solution was disabling automatic login in IE (under the security zone --> custom level --> prompt for username and password as the bottom). Access the site, it will ask for username and password, enter your own and make sure the correct user is displayed. Then set the security zone properties back to what it was. Some kind of weird identity caching in IE.