JSESSIONID issues

[ar-cyber]

Sometimes, the login window STILL doesn't work properly and as such it will not log in correctly. This will require a modification in the session.json file, which isn't ideal.

[AdenMGB]

we need to do a discord screenshare one day and you show us haha

[Crazypersonalph]

Is this due to the new session.json handling (try deleting the session.json and regenerating it), or due to the logic for an expired JSESSIONID not being handled?

[ar-cyber]

Is this due to the new session.json handling (try deleting the session.json and regenerating it), or due to the logic for an expired JSESSIONID not being handled?

It looks that if the OAUTH process does not finish it grabs an invalidated token.

[StroepWafel]

yeah, especially for us who done use SSO, meaning we dont have time to log in manually and so it just closes and sh*ts itself

[ar-cyber]

Converting this to a discussion...

[StroepWafel]

still busted for schools that don't use SSO, instead opting for the default password+email.
If we want a working product this needs to be fixed ASAP it just opens the login page, then closes it again immediately. This then bricks the application and it stays on the "Welcome to DesQTA" page, and the sign-in button stops working

pinging @AdenMGB since we talked about this in the discord too