On Monday, March 16, 2015, Lasitha Wattaladeniya <lasit...@wso2.com> wrote:

> Hi Lakshani,
>
> Even if the SessionDataPersist/RememberMe is not enabled the logged in
> user details will be available in the cache (session data will be removed
> after a time out period). In general session data will be available in
> cache and also in the session persist database.
>

> Therefore you don't have to forcefully put everything to the db, you can
> access from both cache and db.
>

+1
I think using this info we can show some metadata like 'active',
'persisted' for each user sessions.

With this info user can revoke all persisted(remember me enabled) sessions
if he want. And user can check what are the active sessions established.

Btw this feature will be really cool if we can show the ip and the
user-agent\browser which this session is established. AFAIK, we do not
maintain this data currently, if so lets add it into roadmap as a
improvement.

Thanks,
Darshana.


> On Mon, Mar 16, 2015 at 1:42 AM, Lakshani Gamage <laksh...@wso2.com
> <javascript:_e(%7B%7D,'cvml','laksh...@wso2.com');>> wrote:
>
>> Hi all,
>> I'm working on my fast track project [1]. I have to monitor logged in
>> users via  IS admin console. In the current implementation, logged in user
>> details are saved in database if
>> DBCPersistenceManager.SessionDataPersist.Enable = true. For that we have
>> to enable below config in identity.xml.
>>
>> <JDBCPersistenceManager>
>>         <SessionDataPersist>
>>             <Enable>true</Enable>
>>             <RememberMePeriod>60</RememberMePeriod>
>>             <CleanUp>
>>                 <Enable>false</Enable>
>>                     <Period>1</Period>
>>                     <TimeOut>60</TimeOut>
>>             </CleanUp>
>>             <Temporary>false</Temporary>
>>         </SessionDataPersist>
>>     </JDBCPersistenceManager>
>>
>> When above config is not enabled, when a user logs in, that user
>> information is not saved in database. As I have to monitor all the logged
>> in user details, I removed the
>> DBCPersistenceManager.SessionDataPersist.Enable condition checking part
>> from implementation of  authentication-framework component.  Is this ok?
>>
>> [1]. https://redmine.wso2.com/issues/3188
>>
>> Thank you.
>> --
>> Lakshani Gamage
>>
>> *Software Engineer*
>> Mobile : +94 (0) 71 5478184 <%2B94%20%280%29%20773%20451194>
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org <javascript:_e(%7B%7D,'cvml','Dev@wso2.org');>
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Lasitha Wattaladeniya
> Software Engineer
> WSO2, Inc. | http://wso2.com
> lean. enterprise. middleware
>
> Mobile : +94719397528
> Blog : techreadme.blogspot.com
>


-- 
Regards,


*Darshana Gunawardana*Software Engineer
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com <darsh...@wso2.com>*
*Mobile: +94718566859*Lean . Enterprise . Middleware
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to