What is your product version? = API: v11.2.1 | Client: v11.2.1 [20241119] What is your product type? = Angular What is product framework type? = .net core
Hi Team,
We able to enable auto logout for concurrent login for non production environment with one application server and its working as expected.
However, for production environment with multiple application servers and load balancer in place, the auto logout is not working as per expected. Is there any fine tuning needed to be perform so that we can have have auto logout for concurrent login?
3 Answer(s)
-
0
Hi,
If you are your app with multiple instances, you should make some configurations. Please read https://docs.aspnetzero.com/aspnet-core-angular/latest/Clustered-Environment. I think this case is related to
SignalRbut you may face other problems as well.Markdown is supportedCopy & paste or drag & drop images (max 30 MB per image) -
0
Hi,
If you are your app with multiple instances, you should make some configurations. Please read https://docs.aspnetzero.com/aspnet-core-angular/latest/Clustered-Environment. I think this case is related to
SignalRbut you may face other problems as well.Thank you for the suggestion. As for now, we did not use signalR for notification and chat. The only issue that we are facing is on auto logout for concurrent login. Can let us know how to fix this issue?
Markdown is supportedCopy & paste or drag & drop images (max 30 MB per image) -
0
Hi,
Since you are using multiple instances, you need to implement https://docs.aspnetzero.com/aspnet-core-angular/latest/Clustered-Environment#scaling-signalr. Otherwise, logout notification will be sent to specific instances and not all instances.
Markdown is supportedCopy & paste or drag & drop images (max 30 MB per image)
