|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 360 | minor | always | 08-19-05 00:00 | 11-30-05 14:42 | |
|
|
|||||
| Reporter: | sam | Platform: | |||
| Assigned To: | OS: | ||||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | 3.0.14 | ||
| Product Build: | 3.0.14 | Resolution: | fixed | ||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0.15 | ||
|
|
|||||
| Summary: | 0000360: single signon, timeout in one application affects others | ||||
| Description: |
RSN-404 (rep by K Wimmer) With single signon, a timeout in application a kills the login for application b even if application b is in use. Attached is an example that illustrates the problem. Using the attached WAR files and resin.conf: 1. go to http://localhost:8080/a/test.jsp [^] 2. log in with the following credentials: username: Draco Malfoy password: pureblood 3. go to http://localhost:8080/b/test.jsp [^] (subsequent login is not necessary due to SSO) 4. continually refresh the http://localhost:8080/b/test.jsp [^] page for 1 min (the session timeout duration) 5. after 1 min, the session from application 'a' times out and logs you out of both applications 'a' and 'b' (even though the access log will confirm that you just accessed application 'b') The user is prematurely logged out of application 'b'. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||