[MGNLSSO-87] Infinite loop with Okta Created: 18/Nov/21  Updated: 17/Feb/22  Resolved: 17/Feb/22

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

Type: Bug Priority: Neutral
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLSSO-92 Infinite redirection loop after "Conn... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

We noticed this issue in our own cloud first, and then in the following Okta forum post: https://devforum.okta.com/t/magnolia-sso-single-sign-on-with-okta-too-many-redirects/18031

CLOUD-960 has a nice summary about the issue.

Also, the following commit helped to avoid the issue right after logout: https://git.magnolia-cms.com/projects/ENTERPRISE/repos/magnolia-sso/commits/a7698bbf1fe17e361456aac3b8a8d9caa5487d90

The problem still happened when the Magnolia session expired, thus why we aligned the sessions increasing Magnolia's up to 2 hours.

Which unfortunately still didn't fix the issue completely.



 Comments   
Comment by Matt Rajkovic [ 17/Feb/22 ]

Closed as there's a much more up to date ticket: https://jira.magnolia-cms.com/browse/MGNLSSO-92

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