Closed sgauruseu closed 4 years ago
Case 1. Theoretically you need to wait infinite amount of time to get session expired, due to status ping. Need better explanation.
Case 2. Is less valuable as servers don't get restarted often in production often (currently)
Either way fixing this bug would prevent us from correctly implementing #7924 and #7529
Not entirely correct, the session would time out if you are disconnected for a while. However, the idea behavior should be discussed
@sgauruseu and I discussed it internally. The correct behavior may depend on an application: in CS it would be best to show a toast saying that game is over and it is best to copy paste big parts of texts somewhere else and relogin. in Users app due to its security nature and not so much work to loose - redirect to login is probably a good idea. Applications app also doesn't do much about connection loose/session expiration, but maybe it is least important one.
Anyway XP can do little to nothing how frontend should proceed connection or permission loss.
So, we agreed that @sgauruseu will file issues for improvements for each application individually.
Case 1 Set
session.timeout = 2
incom.enonic.xp.web.jetty.cfg
then restart XPType a name - Save button is enabled. Refresh the wizard in browser - Login Page loads
Case 2 The same issue after you stop the server then restart it again.
Actual - Browse panel (previous session) is available, click on New button - New Content dialog loads: