Openbravo Issue Tracking System - Retail Modules
View Issue Details
0043385Retail ModulesWeb POSpublic2020-03-02 14:222020-03-18 15:32
jorge_acosta 
Retail 
highmajoralways
newopen 
5
 
 
No
0043385: Backoffice sessions are not using the timeout when initiate them from POS
If a backoffice session is initiate fomr the POS the session doesn't follow the configured timeout of the backoffice. If the webPOS session is closed then the timeout is followed. Sessions in Backoffice and webPOS should be independent.
- In any version configure a timeout in backoffice of 1 min.
- Do ant smartbuild
- Check the timeout is followed when iniating from backoffice
- Check that if it's initiated from webPOS the session doesnt end.
No tags attached.
Issue History
2020-03-02 14:22jorge_acostaNew Issue
2020-03-02 14:22jorge_acostaAssigned To => Retail
2020-03-02 14:22jorge_acostaResolution time => 1584918000
2020-03-02 14:22jorge_acostaTriggers an Emergency Pack => No
2020-03-18 15:32marvintmResolution time1584918000 =>
2020-03-18 15:32marvintmNote Added: 0118678
2020-03-18 15:32marvintmTypedefect => design defect

Notes
(0118678)
marvintm   
2020-03-18 15:32   
With the current Openbravo architecture, it is not possible to have independent sessions for each of our applications. Therefore, if a session is created from the WebPOS, it is indeed considered a WebPOS session, and will expire only according to WebPOS-specific rules.

Although it is indeed an undesirable situation, it is not really possible for us to change it unless deeper changes are done in the platform and stack.