-
Enhancement
-
Resolution: Done
-
Major
-
None
This relates to ELY-2589.
We should add a test case for the following scenario:
1. Launch with attached standalone xml, keystore, and ear deployment
2. Attempt following requests:
a. http://localhost:8080/app1/session.jsp (login alice:alice)
b. http://localhost:8080/app2/session.jsp
c. http://localhost:8080/app1/invalidate.jsp
d. http://localhost:8080/app1/session.jsp (login again)
e. http://localhost:8080/app2/session.jsp (this should be associated with a different session ID than the one from step b))
- clones
-
JBEAP-25796 [GSS](7.4.z) ELY-2589 - Elytron SSO does not expire other application sessions for session invalidation like Undertow SSO promptly following sessionid change
- Closed
-
ELYWEB-222 Add a test for single sign on across two apps
- Resolved
- is incorporated by
-
JBEAP-26588 (8.0.z) Upgrade Elytron Web from 4.0.0.Final-redhat-00001 to 4.0.1.Final-redhat-00001
- Closed
- relates to
-
JBEAP-26258 [GSS](8.0.z) ELY-2589 - Elytron SSO does not expire other application sessions for session invalidation like Undertow SSO promptly following sessionid change
- Closed