Project:
| View Revisions: Issue #41344 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0041344: After HTTP Session timeout, new requests from Web POS cause the insertion of a record in AD_SESSION with username NULL | ||
| Revision | 2019-07-31 15:46 by alostale | ||
| Steps To Reproduce | 1. Setup the session timeout to 1 minute either in Tomcat or the load balancer (if there is one) 2. Log on to Web POS and start the creation of a ticket 3. Wait for the HTTP session to expire 4. Perform any action that generates a request to the server (i.e.: search for a business partner) 5. Query AD_SESSION for records created in the past few minutes, there will be two records from the terminal in use, one with the appropriate data and one as described above Questionable behavior: - With DefatultAuthenticantionManager, after Tomcat expires session, user is requested to log in again. With MobileKeyAuthenticationManager they are transparently logged in. Incorrect behavior: - New session created in AD_Session - This new session is of type S which consumes backend user - This session lacks some info (username...) |
||
| Revision | 2019-07-31 15:41 by alostale | ||
| Steps To Reproduce | 1. Setup the session timeout to 1 minute either in Tomcat or the load balancer (if there is one) 2. Log on to Web POS and start the creation of a ticket 3. Wait for the HTTP session to expire 4. Perform any action that generates a request to the server (i.e.: search for a business partner) 5. Query AD_SESSION for records created in the past few minutes, there will be two records from the terminal in use, one with the appropriate data and one as described above |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |