"You have reached maximum allowed number of concurrent sessions "

Another Thought I had:

If your platform is a multiple node instance, then it is possible to log in to one node. Exit your internet browser. Go to your environment, but be routed to a different node. Now you have two concurrent sessions on two nodes, but without editing your cookies (to directly hit the node you want), you can not access the first node to log off. Rinse, repeat, and if you're unlucky, you'll be connected to a third different node.

Best way to mitigate a multiple node logins resulting in max concurrent sessions is to have a low idle timeout session. In this way, any node you are still logged into, will timeout in a reasonable time, allowing a new login. You could also consider having your concurrent sessions = to the number of nodes for you system.

Another Thought I had:

If your platform is a multiple node instance, then it is possible to log in to one node. Exit your internet browser. Go to your environment, but be routed to a different node. Now you have two concurrent sessions on two nodes, but without editing your cookies (to directly hit the node you want), you can not access the first node to log off. Rinse, repeat, and if you're unlucky, you'll be connected to a third different node.

Best way to mitigate a multiple node logins resulting in max concurrent sessions is to have a low idle timeout session. In this way, any node you are still logged into, will timeout in a reasonable time, allowing a new login. You could also consider having your concurrent sessions = to the number of nodes for you system.