1

While the answer here is fine for one or a couple of users: ASP.net Identity 2.0 Sign-out another user it does not really scale, it can take a lot of time: https://msdn.microsoft.com/en-us/library/dn497517(v=vs.108).aspx

I am thinking about SignalR forcing a refresh on the client and making a temporary change in the routing but not sure this is the right way of doing.

Notes:
- It would be for maintenance purposes.
- I don't want to stop the application, it would be some occasional data synchronization with some other external systems.

Natalie Perret
  • 8,013
  • 12
  • 66
  • 129
  • if you're going to sign everyone out, what's the difference between that and stopping the web app, in practical terms? – ADyson Jan 05 '18 at 09:53
  • @ADyson let's say I want admin users to be still able to log in for maintenance purposes in addition to some synchronization. My purpose here does not really matter. I am more curious in a solution, like is there is a better solution than looping through a lot of users and update the security stamp which from my experience takes really long. Any routing trick? – Natalie Perret Jan 07 '18 at 00:35
  • I don't know the size/complexity of this piece of software but iIn larger web applications the admin functionality would be in a separate app and you would be able to leave that switched on, along with any background services if necessary. So you could shut down the user-facing interfaces and services without affecting other parts of the operation. BTW I read about the sign out method you linked to - why would it take a long time? It suggests it should immediately invalidate the cookies if you set the refresh interval to something very short (a few seconds) – ADyson Jan 07 '18 at 05:53

0 Answers0