Bug 798210 - [RFE] LastLoginTime should be configurable
Summary: [RFE] LastLoginTime should be configurable
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal
Version: 6.0.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER02
: 6.1.0
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-28 10:33 UTC by bkramer
Modified: 2023-02-27 08:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
In versions prior to Red Hat JBoss Portal (JBoss Portal) 6.1, the lastLoginTime property was always updated each time a user successfully authenticated on the platform. For customers with a large number of concurrent users, updating this property caused performance issues surrounding write operations on the PicketLink IDM database. In JBoss Portal 6.1, a new configuration option in 'JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/idm-configuration.xml' controls how a user's last login time is recorded in the PicketLink IDM database. [source,XML] ---- <!-- If true, the property lastLoginTime of user will be updated after successful authentication of this user to portal.--> <!-- If false, the property won't be updated, which could have performance improvement in systems with many concurrent user logins --> <field name="updateLastLoginTimeAfterAuthentication"> <boolean>false</boolean> </field> ---- The property is true by default, which makes the enhancement backwards compatible with previous versions.
Clone Of:
Environment:
Last Closed:
Type: Enhancement
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNPORTAL-3108 0 Major Resolved LastLoginTime should be configurable 2019-02-18 10:29:02 UTC

Description bkramer 2012-02-28 10:33:29 UTC 
Description of problem:

It would be good to have ability to configure (disable/enable) the LastLoginTime writing on database when a user logs in the portal. 

Currently lastLoginTime is always updated and this can make a problem when running a test with the big number of simultaneous users that are using the same username/password.  

The lastLoginTime is updated in authenticate() method of the UserDAOImpl [1].


[1] http://anonsvn.jboss.org/repos/gatein/epp/portal/tags/EPP_5_1_1_GA/component/identity/src/main/java/org/exoplatform/services/organization/idm/UserDAOImpl.java


Version-Release number of selected component (if applicable):
EPP 5.2
Comment 2 Dominik Pospisil 2013-08-01 13:04:49 UTC 
Verified (ER3).
Note You need to log in before you can comment on or make changes to this bug.