Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0040734Retail ModulesSessionspublic2019-04-30 17:042019-04-30 18:39
Reportersalvador_campanella 
Assigned ToRetail 
PrioritynormalSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product VersionRR18Q3.3 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0040734: Restrict User to a Single Login Instance not working for POS and Backoffice
DescriptionRestrict User to a Single Login Instance not working for POS and Backoffice

Exist a old issue with this topic
https://issues.openbravo.com/view.php?id=30883 [^]

In the repository this change was made in the revision: 34151
Steps To Reproduce1. 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
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2019-04-30 17:04salvador_campanellaNew Issue
2019-04-30 17:04salvador_campanellaAssigned To => Retail
2019-04-30 17:04salvador_campanellaTriggers an Emergency Pack => No
2019-04-30 17:22shuehnerNote Added: 0111402
2019-04-30 18:39johnfandlNote Added: 0111403

Notes
(0111402)
shuehner   
2019-04-30 17:22   
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
login.limit.user.session=false
hg cat -r 3.0PR18Q3 config/Openbravo.properties.template | grep limit.user


Or similar can be used to see when it was removed.
(0111403)
johnfandl   
2019-04-30 18:39   
RE:

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