[MGNLLIC-44] As a user I am signaled if I use a demo or an unlicensed system so that I know that I work with a limited feature set Created: 27/Aug/13  Updated: 16/Nov/15  Resolved: 16/Nov/15

Status: Closed
Project: Magnolia License
Component/s: Checker
Affects Version/s: 1.4-beta1
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Espen Jervidalo Assignee: Unassigned
Resolution: Obsolete Votes: 1
Labels: None
Remaining Estimate: 2d
Time Spent: Not Specified
Original Estimate: 2d

Issue Links:
supersession
supersedes MGNLEE-278 Warning when near license expiration ... Closed
is superseded by MGNLEE-418 Report error in Pulse if product lice... Closed
is superseded by MGNLEE-419 Warn in Pulse if product license expi... 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)
Date of First Response:

 Comments   
Comment by Andreas Weder [ 21/Jul/15 ]

Just happened to me and cost me a lot of time: I downloaded 5.4 and installed my EE pro license without realizing that it was past the expiration date. Magnolia did not prevent me from installing an invalid license, nor did it warn me about it.

I did notice that the personalization module raised a warning in the Pulse message log. I also noticed that I got the "no valid license found for MultiSite" in the logs. When I checked the "About Magnolia" app to check my license, though, I did not realize the bad date either: I expected some kind of warning or error indicator.

In the end, I started debugging a "problem" with the MTE demo, which was also caused by the expired license, though that wasn't obvious (tour detail pages caused a 404), when I finally noticed what was happening.

While this was clearly a user error, we must improve how we deal with license expiration. We should:

  • prevent an administrator from installing an invalid license
  • clearly indicate an invalid or expired license in the "About Magnolia" app
  • eventually even show a warning or error, if a license has expired
  • notice the administrators (see MGNLLIC-43) well in advance when a license is about to expire by sending daily messages to Pulse.
Comment by Andreas Weder [ 16/Nov/15 ]

I'm closing this issue as we've created two separate issues under a common epic covering both the warning that should be sent in advance and the error sent when the license has expired.

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