[JBoss JIRA] (GTNPORTAL-3184) Not allowing the same user login in at the same time (two sessions)
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3184?page=com.atlassian.jira.pl... ]
Vu Viet Phuong commented on GTNPORTAL-3184:
-------------------------------------------
There are 2 related registry services : ConversationRegistry and IdentityRegistry. They can't clear the relate ConversationState and Identity object after user has logged out
> Not allowing the same user login in at the same time (two sessions)
> -------------------------------------------------------------------
>
> Key: GTNPORTAL-3184
> URL: https://issues.jboss.org/browse/GTNPORTAL-3184
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Identity integration, Security
> Affects Versions: 3.6.0.Final
> Reporter: Trong Tran
> Assignee: Vu Viet Phuong
> Labels: portal-s72, worked
> Fix For: 3.7.0.Final
>
> Original Estimate: 1 day, 4 hours
> Time Spent: 1 day
> Remaining Estimate: 4 hours
>
> In the DefaultLoginModule, it supports to set "singleLogin" option parameter which disallows the same user to login to use the portal at the same time from different browsers/machines
> Unfortunately it doesn't work properly. I can not login with the same user after logged-out.
> Moreover, the GateIn documentation is also missing this part. I think we could add this information in the section https://docs.jboss.org/author/display/GTNPORTAL36/Authentication+and+Auth...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (GTNPORTAL-3184) Not allowing the same user login in at the same time (two sessions)
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3184?focusedWorklogId=12429498&... ]
Vu Viet Phuong logged work on GTNPORTAL-3184:
---------------------------------------------
Author: Vu Viet Phuong
Created on: 17/Jul/13 11:48 PM
Start Date: 17/Jul/13 11:48 PM
Worklog Time Spent: 1 day
Issue Time Tracking
-------------------
Remaining Estimate: 4 hours (was: 1 day, 4 hours)
Time Spent: 1 day
Worklog Id: (was: 12429498)
> Not allowing the same user login in at the same time (two sessions)
> -------------------------------------------------------------------
>
> Key: GTNPORTAL-3184
> URL: https://issues.jboss.org/browse/GTNPORTAL-3184
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Identity integration, Security
> Affects Versions: 3.6.0.Final
> Reporter: Trong Tran
> Assignee: Vu Viet Phuong
> Labels: portal-s72, worked
> Fix For: 3.7.0.Final
>
> Original Estimate: 1 day, 4 hours
> Time Spent: 1 day
> Remaining Estimate: 4 hours
>
> In the DefaultLoginModule, it supports to set "singleLogin" option parameter which disallows the same user to login to use the portal at the same time from different browsers/machines
> Unfortunately it doesn't work properly. I can not login with the same user after logged-out.
> Moreover, the GateIn documentation is also missing this part. I think we could add this information in the section https://docs.jboss.org/author/display/GTNPORTAL36/Authentication+and+Auth...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (GTNPORTAL-3184) Not allowing the same user login in at the same time (two sessions)
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3184?page=com.atlassian.jira.pl... ]
Vu Viet Phuong commented on GTNPORTAL-3184:
-------------------------------------------
When turn-on singleLogin, only after user has logout on one browser, he can login on other browser.
This machanism rely on IdentityRegistry, and JAASConversationStateListener --> a HttpSession listener
when user logout, the sessionDestroyed event is dispatched and this listener will clear the coressponding identity object in the registry
in WCI (TC7ServletContainerContext class) we have logout code like this:
{code}
//This will change the sessionID
servletRequest.logout();
...
//This code dispatch sessionDistroyed event
webapp.invalidateSession();
...
{code}
The JAASConversationStateListener receive session destroyed event but with a difference sessionID. Then it can not remove the corresponding identity object in the registry
User can not login again, even after the has logout. And this also cause memory leak in the IdentityRegistry service
> Not allowing the same user login in at the same time (two sessions)
> -------------------------------------------------------------------
>
> Key: GTNPORTAL-3184
> URL: https://issues.jboss.org/browse/GTNPORTAL-3184
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Identity integration, Security
> Affects Versions: 3.6.0.Final
> Reporter: Trong Tran
> Assignee: Vu Viet Phuong
> Labels: portal-s72
> Fix For: 3.7.0.Final
>
> Original Estimate: 1 day, 4 hours
> Remaining Estimate: 1 day, 4 hours
>
> In the DefaultLoginModule, it supports to set "singleLogin" option parameter which disallows the same user to login to use the portal at the same time from different browsers/machines
> Unfortunately it doesn't work properly. I can not login with the same user after logged-out.
> Moreover, the GateIn documentation is also missing this part. I think we could add this information in the section https://docs.jboss.org/author/display/GTNPORTAL36/Authentication+and+Auth...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months