You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering a significant issue with authentication in my Blazor application hosted on a Windows Server within a LAN environment.
Problem Description:
Whenever I turn off the IIS server to install updates for the application and then turn it back on, users find themselves logged into incorrect accounts. For example, I might be logged in as Admin, but after the restart, I find myself connected as a different user. This issue affects all users on the LAN, causing them to be logged in as different accounts, not their own. Additionally, the logout function ceases to work properly when this happens.
Server Environment: The application is hosted on a server that is part of an Active Directory (AD) domain.
Has anyone experienced a similar issue or have any insights on what might be causing this problem? Any advice or suggestions would be greatly appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I'm encountering a significant issue with authentication in my Blazor application hosted on a Windows Server within a LAN environment.
Problem Description:
Whenever I turn off the IIS server to install updates for the application and then turn it back on, users find themselves logged into incorrect accounts. For example, I might be logged in as Admin, but after the restart, I find myself connected as a different user. This issue affects all users on the LAN, causing them to be logged in as different accounts, not their own. Additionally, the logout function ceases to work properly when this happens.
Here are additional details about my setup:
IIS Server Version: 10.0.17763.1
Authentication Method: ASP.NET Authentication
Server Environment: The application is hosted on a server that is part of an Active Directory (AD) domain.
Has anyone experienced a similar issue or have any insights on what might be causing this problem? Any advice or suggestions would be greatly appreciated.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions