[MGNLEE-206] Make the license key update more user friendly Created: 13/Jun/11  Updated: 10/Mar/17  Resolved: 26/Nov/13

Status: Closed
Project: Magnolia DX Core
Component/s: registration
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Zdenek Skodik Assignee: Magnolia International
Resolution: Outdated Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLEE-204 Entering a license fails if the licen... Closed
dependency
is depended upon by MGNLLIC-49 PathNotFoundException when license no... Closed
duplicate
duplicates MGNLEE-38 Add a page for updating the license Closed
relation
is related to MGNLEE-38 Add a page for updating the license 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:

 Description   

From time to time there are reported troubles during the license update via /modules/enterprise/license.

It would be nice to prevent such scenarios by providing a Tools page with a simple entry form available all the time. Such form would do a key validation prior to taking it into account and as best it would also provide an information on when the current license expires.



 Comments   
Comment by Philip Mundt [ 26/Nov/13 ]

See: MGNLEE-327

Generated at Mon Feb 12 05:27:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.