Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0043385 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
design defect | [Retail Modules] Web POS | major | always | 2020-03-02 14:22 | 2020-03-18 15:32 | |||||||
Reporter | jorge_acosta | View Status | public | |||||||||
Assigned To | Retail | |||||||||||
Priority | high | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Review Assigned To | ||||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0043385: Backoffice sessions are not using the timeout when initiate them from POS | |||||||||||
Description | 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. | |||||||||||
Steps To Reproduce | - 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. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0118678) marvintm (manager) 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. |
Issue History | |||
Date Modified | Username | Field | Change |
2020-03-02 14:22 | jorge_acosta | New Issue | |
2020-03-02 14:22 | jorge_acosta | Assigned To | => Retail |
2020-03-02 14:22 | jorge_acosta | Resolution time | => 1584918000 |
2020-03-02 14:22 | jorge_acosta | Triggers an Emergency Pack | => No |
2020-03-18 15:32 | marvintm | Resolution time | 1584918000 => |
2020-03-18 15:32 | marvintm | Note Added: 0118678 | |
2020-03-18 15:32 | marvintm | Type | defect => design defect |
Copyright © 2000 - 2009 MantisBT Group |