[MGNLSSO-298] Module update tasks not working in SSO > 3.1.0 Created: 27/Jul/23  Updated: 25/Aug/23  Resolved: 23/Aug/23

Status: Closed
Project: Single Sign On
Component/s: None
Affects Version/s: 3.1.0, 3.1.1, 3.1.3, 3.1.4, 3.1.5
Fix Version/s: saas, 3.1.6

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

Issue Links:
Relates
relates to MGNLSSO-300 Role sso-redirect-uri-authorizer does... Accepted
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:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: SSO maintenance
Team: AdminX
Work Started:

 Description   

Steps to reproduce

  1. Install any SSO module < 3.1.0 (before the introduction of MGNLSSO-188)
  2. Update to any version >= 3.1.0

Expected results

The module should run it's update tasks upon installation.

Actual results

The module runs it's installation tasks instead.

Workaround

N/A

Development notes

The issue is due to the fact the update mechanism relies on the module name and installed version.
Due to MGNLSSO-188, SSO modules >=3.1.0 were renamed from magnolia-sso to sso, thus rendering the update mechanism inop.



 Comments   
Comment by Fabian Mangold [ 27/Jul/23 ]

Reference:
https://magnolia-cms.slack.com/archives/C0140J1BJ5U/p1690316937200829
https://magnolia-cms.slack.com/archives/C0140J1BJ5U/p1690321208617529

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