Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0031009 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [Retail Modules] Web POS | minor | have not tried | 2015-10-01 16:42 | 2015-10-01 17:35 | |||||||
| Reporter | plujan | View Status | public | |||||||||
| Assigned To | Retail | |||||||||||
| Priority | normal | 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 | main | SCM revision | ||||||||||
| Review Assigned To | ||||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0031009: [RR15Q4] It is possible to keep a POS session active that will conflict with next logins attemps | |||||||||||
| Description | On the first login after updating from 15Q3 to 15Q4 I've got a message saying that I was already logged in. The message is not clear enough to understand what was happening and should be updated. | |||||||||||
| Steps To Reproduce | NOTE: Since original steps are not clear, this is an alternate way of getting the same message. 1. Go to webPOS login page 2. Log in as vallblanca user. Check that you are taken to the main webPOS screen. 3. Open a new tab, go again to webPOS login page 4. Try to login as a different user. A message is shown: Session for the ERP already exists You have already logged in the ERP in this browser. Therefore, you cannot log in. If the ERP session is valid for this application, you only need to refresh the page. If not, you need to log out of the ERP before you can log in. | |||||||||||
| Proposed Solution | Note that: *The message says I have a session in the ERP, while steps do not involve backend access in any way. *If I press F5, I am logged in as vallblanca user, while after step 4 I was trying to access with a different user. A better way to deal with this situation is not to assume a valid active session means the user has logged in the backend, and not to assume the same user will be trying to login again. I'd suggest to change the message to: "An active session has been detected, you may choose to keep previous session or create a new one" with two buttons to either refresh the screen and use current session or to kick the old session and create a new one. | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files |  ActiveSession.png [^] (97,648 bytes) 2015-10-01 16:42
| |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2015-10-01 16:42 | plujan | New Issue | |
| 2015-10-01 16:42 | plujan | Assigned To | => Retail |
| 2015-10-01 16:42 | plujan | File Added: ActiveSession.png | |
| 2015-10-01 16:42 | plujan | Triggers an Emergency Pack | => No |
| 2015-10-01 17:35 | plujan | Summary | It is possible to keep a POS session active that will conflict with next logins attemps => [RR15Q4] It is possible to keep a POS session active that will conflict with next logins attemps |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |