I am trying out concurrentSessionController and I see the following behavior. I am not sure if this the right behavior or not
(1) Lets say I log into the app as user1/user1_password.
(2) Open another browser, and log in as user1/user1_password
(3) Click on any link in the browser session created in step 1, I will be redirected to session Invalid page.
So my question is, shouldn't step 2 fail because there is already an active session associated with the same user