Unable to login. Multiple login limit for the same user account has been reached

I have enable “Enable Multiple Logins” and set count to 2.
when i tries to do 3rd login it say " Multiple login limit for the same user account has been reached" which is correct. This works perfectly.

But can i do something like this when user tries to do 3rd login, logout from first user/device. So user can access 2 logins only (2nd and 3rd)
login

Hello @Swapnil_G

Now there is no such possibility. I’ve created an internal ticket BKNDLSS-30077 to discuss adding this feature.

Regards

Okay Thanks @viktor.liablin
Please post here once you get a solution or if any other suggestion to handle this case

What would be an example in the real world when such behavior is useful? If the login is shared by multiple people and one logs in first, then sometime later they are suddenly logged out because someone else, somewhere logged in with the same credentials. I do not quite understand in what use case it would make sense.

Regards,
Mark

This is on a very old post, but I can provide the use-case for OP’s question:

Sometimes you want to access an app or website on multiple personal devices, such as a phone and laptop, but you don’t want to be required to login again whenever you switch devices. In that scenario, setting a maximum number of sessions for a user to three, for example, can make it possible while still keeping concurrent sessions fairly low.

Hello @Adam_Cook

Thanks for sharing your perspective — it definitely highlights a practical use case for allowing multiple sessions per user, like accessing the app from a phone and a laptop without needing to re-login every time.

That said, I think your example sheds light on the topic from a slightly different angle compared to what the original poster (OP) was asking. The OP already has the option to allow 2 simultaneous sessions, but was wondering if — upon a third login — the oldest session could automatically be logged out, keeping the session count within the limit.

In your case, it sounds like simply increasing the allowed number of concurrent sessions (e.g., to 3) already solves the problem. Do you think your use case is fully covered just by raising the session limit, or were you suggesting something more specific beyond that?

Regards,
Volodymyr

Hi @Volodymyr_Ialovyi,

In my use-case I was trying to point out a scenario where the OPs request would be ideal. For example, if the limit was two and I was logged in on my computer and my phone, but then I went to log in on another device, I’d like the oldest session to be invalidated.

The idea is to have the best of both worlds. Allow multiple sessions with more graceful limits. I think the current way would be frustrating for a user, and even potentially lock them out of their account if they don’t have access to a previous device.

Hello @Adam_Cook

Thanks, that makes it clear! So you’re fully supporting the idea originally raised by the OP — having the ability to automatically invalidate the oldest session when a new login exceeds the session limit.

Really appreciate you sharing your perspective on this — insights like yours help make the product better. We’ll definitely take your feedback into account.

Regards,
Volodymyr

1 Like