Back to bug 798210
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| bkramer | 2012-02-28 10:35:18 UTC | Type | --- | Enhancement |
| hfnukal | 2012-06-06 11:38:37 UTC | Target Release | --- | 6.0.x |
| CC | hfnukal | |||
| Component | Portal | Portal | ||
| Version | 5.2.x | 6.0.x | ||
| Assignee | jbpapp-maint | mposolda | ||
| Product | JBoss Enterprise Portal Platform 5 | JBoss Enterprise Portal Platform 6 | ||
| Martin Weiler | 2012-08-16 09:29:00 UTC | CC | mweiler | |
| Boleslaw Dawidowicz | 2013-04-17 09:05:50 UTC | CC | bdawidow | |
| Assignee | mposolda | jbpapp-maint | ||
| Boleslaw Dawidowicz | 2013-06-11 09:34:51 UTC | CC | mposolda | |
| Link ID | JBoss Issue Tracker GTNPORTAL-3108 | |||
| Status | NEW | ASSIGNED | ||
| Target Release | 6.0.x | 6.1.0 | ||
| Assignee | jbpapp-maint | mposolda | ||
| Boleslaw Dawidowicz | 2013-06-11 13:30:01 UTC | Status | ASSIGNED | MODIFIED |
| Assignee | mposolda | jbpapp-maint | ||
| Doc Text | Cause: In versions prior to JPP 6.1 we always update lastLoginTime property of user after successful authentication of this user to JPP. But some customers which doesn't need lastLoginTime info and have big number of concurrent users doesn't want to | |||
| Doc Text | update it because each update of lastLoginTime requires write operations to Picketlink IDM database | |||
| Doc Text | , which means some performance penalty Consequence: Fix: In JPP 6.1 we are providing new configuration option in file JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/idm-configuration.xml : <!-- If true | |||
| Doc Text | , the property lastLoginTime of user will be updated after successful authentication of this user to portal. If false, the property won't be updated | |||
| Doc Text | , which could have performance improvement in systems with many concurrent user logins --> <field name="updateLastLoginTimeAfterAuthentication"> <boolean>false</boolean> </field> So the property is true by default | |||
| Doc Text | , which is backwards compatible with previous versions. But people have possibility to disable update of lastLoginTime by switch this option to "false" | |||
| Doc Type | Bug Fix | Enhancement | ||
| Target Milestone | --- | ER02 | ||
| hfnukal | 2013-07-04 12:27:06 UTC | Status | MODIFIED | ON_QA |
| Jared MORGAN | 2013-07-28 23:48:16 UTC | Doc Text | Cause: In versions prior to JPP 6.1 we always update lastLoginTime property of user after successful authentication of this user to JPP. But some customers which doesn't need lastLoginTime info and have big number of concurrent users doesn't want to update it because each update of lastLoginTime requires write operations to Picketlink IDM database, which means some performance penalty Consequence: Fix: In JPP 6.1 we are providing new configuration option in file JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/idm-configuration.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> So the property is true by default, which is backwards compatible with previous versions. But people have possibility to disable update of lastLoginTime by switch this option to "false" | In versions prior to JBoss Portal Platform (JPP) 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 JPP 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. |
| Dominik Pospisil | 2013-08-01 13:04:49 UTC | Status | ON_QA | VERIFIED |
| CC | dpospisi | |||
| Jared MORGAN | 2013-09-24 05:29:50 UTC | Doc Text | In versions prior to JBoss Portal Platform (JPP) 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 JPP 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. | 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. |
| PnT Account Manager | 2018-02-06 19:18:47 UTC | CC | hfnukal | |
| PnT Account Manager | 2019-01-01 03:41:14 UTC | CC | dpospisi | |
| Jeff Fearn 🐞 | 2020-04-27 01:31:49 UTC | Assignee | jbpapp-maint | nobody |
Back to bug 798210