Comments by Member 14940951

Member 14940951 15-Oct-20 12:21pm View

I have checked multiple times and I am sure, there is no default case scenario set.

Also the issue doesnt occur when we debug the code locally on their machines.
User.Identity.Name fetches right user ids when run locally with code on their machines but gives wrong values when accessing the hosted application(production url).

Member 14940951 15-Oct-20 12:13pm View

I have cross checked and they login with their respective user ids only. There is no shortcut that is set to run as a different account. Also there is no default case scenario set such as when a user is not found, it is filled with another user id.

Member 14940951 15-Oct-20 2:57am View

@ZurdoDev,

When we access the website from a local machine, the expected result is that the application must be authenticated with the current logged in user. But here instead it is authenticated with a different user id (which is an admin account).

In my case, admin account is just another LDAP user account which is used in our daily services with more access rights than a normal user. It is also the account with which the Windows 7 server machine is logged on.

The application works fine as expected for everyone else except in case of the these 2 particular users.

This issue occurs to the above users only while accessing the hosted application(production url). When I debug the application via code locally on their machines, their respective user ids are fetched as expected.

I have also tried clearing the entire browsing data including cookies and cache.

Comments by Member 14940951 (Top 3 by date)