Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 3.2
-
Fix Version/s: 3.2
-
Component/s: Tool Multiple Choice
-
Labels:None
Description
On JBoss shared session (SSO) and HTTP session were different things.
On WildFly they are the same session.
Many tools use SessionMap object to store their attributes, but MC puts them straight into session.
One of MC attributes is "user" which also identifies the logged in user in SSO.
When a learner enters MC, all know attributes are cleared, including "user".
This produces the error and basically logs the user out from LAMS.
On WildFly they are the same session.
Many tools use SessionMap object to store their attributes, but MC puts them straight into session.
One of MC attributes is "user" which also identifies the logged in user in SSO.
When a learner enters MC, all know attributes are cleared, including "user".
This produces the error and basically logs the user out from LAMS.
Activity
MCQ is going the way of the Dodo in v5.0. No need to do this.
The proper solution is to make MC and other tools store their data differently (in SessionMaps for example),
so they do not overlap with each other and core.