Bug 798210

Summary:	[RFE] LastLoginTime should be configurable
Product:	[JBoss] JBoss Enterprise Portal Platform 6	Reporter:	bkramer <bkramer>
Component:	Portal	Assignee:	Nobody <nobody>
Status:	VERIFIED ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.x	CC:	bdawidow, epp-bugs, mposolda
Target Milestone:	ER02
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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).