[MGNLSSO-98] Inconsistent behaviour after "Connection lost. Trying to reconnect..." message Created: 18/Feb/22  Updated: 25/May/22  Resolved: 11/Mar/22

Status: Closed
Project: Single Sign On
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0.0

Type: Bug Priority: Neutral
Reporter: Matt Rajkovic Assignee: Nguyen Phung Chi
Resolution: Fixed Votes: 0
Labels: discovery
Remaining Estimate: Not Specified
Time Spent: 3d 7h
Original Estimate: Not Specified

Attachments: PNG File image (24).png    
Issue Links:
Cloners
is cloned by MGNLSSO-120 Inconsistent behaviour after "Connect... Closed
Relates
causality
relation
is related to MGNLSSO-92 Infinite redirection loop after "Conn... Closed
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:
Sprint: AdminX 5
Story Points: 5

 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


 Comments   
Comment by Nguyen Phung Chi [ 25/May/22 ]

Hey mrajkovic , mgeljic 

I think the fix is applicable for release 2.0 and it's affecting customers too.

So, we should port the fix to release 2.0.

cc efochr 

Comment by Evzen Fochr [ 25/May/22 ]

nguyen.phung I am fine with that, can you please create story ticket for it and add it to adminx team?

Comment by Ervin Vystup [ 25/May/22 ]

I have no idea jbroemmer , sorry. Maybe efochr  could know?

Comment by Evzen Fochr [ 25/May/22 ]

Not sure if it can be applied OOTB. Creating backport ticket for it.

Check progress on MGNLSSO-120

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