[MGNLSSO-120] Inconsistent behaviour after "Connection lost. Trying to reconnect..." message - backport to 2.x Created: 25/May/22  Updated: 05/Sep/22  Resolved: 09/Jun/22

Status: Closed
Project: Single Sign On
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0.4, Tech Prod Ready

Type: Bug Priority: Major
Reporter: Matt Rajkovic Assignee: Evzen Fochr
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLSSO-98 Inconsistent behaviour after "Connect... Closed
Relates
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLSSO-121 Implementation Technical task Completed Evzen Fochr  
MGNLSSO-122 Review Technical task Completed Nguyen Phung Chi  
MGNLSSO-123 PiQA Technical task Completed Nguyen Phung Chi  
MGNLSSO-124 Final QA Technical task Completed Nguyen Phung Chi  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: SSO support for custom IdPs
Sprint: AdminX 11
Story Points: 2
Team: AdminX

 Description   

It seems like we have an issue very similar to https://jira.magnolia-cms.com/browse/MGNLSSO-92

DotFusion reports: 

Main concern that @arjuna raised in our call is that Magnolia is still timing out, and you need to clear cache in order to get back in.
For developers this was annoying, but they can deal with it.
But now its designers and content authors trying to use Magnolia to get their jobs done and its extra-annoying because they often need to go to the devs for help to be able to log in again. (Which is not a great feeling.)I guess that this is going to slowly color peoples feeling towards Magnolia.

D&G reports: 

Matt: Do you still experience the issue when you lose connection to Magnolia after some inactivity and need to clean your cookies before being able to log in again?

@josh: Yes, it doesnt seem to reauth. Dont have to clean cookies anymore, just a double page reload sorts it. Sometimes we get a 500 error page. The error page is attached.

mrajkovic COULDN'T reproduce the issue on relatively new subscription kvzjbtwfqvfok9fp. Even after several hours of inactivity, I was able to log back in just fine on Chrome bowser, clean incognito window. 

Additional info

Consolidated additional info from the previous related ticket https://jira.magnolia-cms.com/browse/MGNLSSO-87 by mmichel

Next steps

  • Asked the DevX team in #saas-try-it-out channel if they reproduced the problem during their two past SaaS testing sessions
  • Asked Josh Beckerleg from D&G to look out for the problem
  • Asked in #pd-cloud for everyone to look out and ping me if they reproduce it

Generated at Mon Feb 12 10:51:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.