|View Issue Details|
|Type||Category||Severity||Reproducibility||Date Submitted||Last Update|
|defect||[Retail Modules] Sessions||major||always||2019-04-30 17:04||2019-04-30 18:39|
|Priority||normal||Resolution||open||Fixed in Version|
|Status||new||Fix in branch||Fixed in SCM revision|
|OS Version||Database version||Ant version|
|Product Version||RR18Q3.3||SCM revision|
|Review Assigned To|
|Regression introduced in release|
|Regression introduced by commit|
|Triggers an Emergency Pack||No|
0040734: Restrict User to a Single Login Instance not working for POS and Backoffice
|Description||Restrict User to a Single Login Instance not working for POS and Backoffice|
Exist a old issue with this topic
In the repository this change was made in the revision: 34151
|Steps To Reproduce||1. In Openbravo.properties file. Set login.limit.user.session=true|
2. Compile and restart tomcat
3. Login to OB Backoffice with User 1
4. Attempt to log intoOB POS with User 1
5. Receive the attached error message [OK] - as expected per the properties setting
6. Click OK button
7. Expect OB to end the other session (from step 3), but that session remains logged on
|Tags||No tags attached.|
Not a regression. That feature was removed as part of 'license cleanup' in 18Q3.
Initially that feature was added to help license compliance with license of type 'named user' only sold if old obsolete ondemand hosting.
As those licenses are obsolete and not used anymore as part of cleaning up licensing code in 18Q3 was feature was removed.
That is also indirectly visible by not having the login.limit.user.session line anymore in the Openbravo.properties template.
hg cat -r 3.0PR18Q2 config/Openbravo.properties.template | grep limit.user
hg cat -r 3.0PR18Q3 config/Openbravo.properties.template | grep limit.user
Or similar can be used to see when it was removed.
"Not a regression. That feature was removed as part of 'license cleanup' in 18Q3.
Initially that feature was added to help license compliance with license of type 'named user' only sold if old obsolete ondemand hosting."
From the partner perspective, this is a regression. When you create a new core platform feature that you document in the wiki, partners build on top of it (relying on it), and then you remove it without any notification at all (essentially breaking partner code) - that is essentially the definition of a regression.
|2019-04-30 17:04||salvador_campanella||New Issue|
|2019-04-30 17:04||salvador_campanella||Assigned To||=> Retail|
|2019-04-30 17:04||salvador_campanella||Triggers an Emergency Pack||=> No|
|2019-04-30 17:22||shuehner||Note Added: 0111402|
|2019-04-30 18:39||johnfandl||Note Added: 0111403|
|Copyright © 2000 - 2009 MantisBT Group|