0040734: Restrict User to a Single Login Instance not working for POS and Backoffice

Notes
(0111402) shuehner (administrator) 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 (reporter) 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.

Relationships [ Relation Graph ] [ Dependency Graph ]