[MAGNOLIA-3559] There is no way to activate back superuser role if it is deactivated Created: 23/Feb/11  Updated: 23/Feb/11  Resolved: 23/Feb/11

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: Chetan Assignee: Jan Haderka
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

There is no way to activate back superuser role if it is deactivated



 Comments   
Comment by Jan Haderka [ 23/Feb/11 ]

Deactivation of the role means removing it from the public instance. If the role contains permissions necessary for given user to activate the content it also means that given user will not be able to activate any content any more.
However should any other user have assigned permissions necessary for activation either directly or via group/role, such user is still able to activate the content and also re-activate the superuser role.

Comment by Chetan [ 23/Feb/11 ]

1) The superuser role is deactivated and not superuser user so user is able to login but not able to activate the superuser role 401 error
2) There is no other user with activation permissions.
3) Now NO new user and role be created, edited and changed , activated by superuser login as superuser role is no more active.

So this is blocker issue if there is no workaround.

Comment by Chetan [ 23/Feb/11 ]

I am not able to reopen this issue in jira ?

Comment by Jan Haderka [ 23/Feb/11 ]

This is not an issue of the product, same way as incorrect editing of groups and permissions of superuser/administrator can result in lockout of such user on the OS level.

If you locked out yourself from the instance, either open a support issue and ask for help on support if you have a support contract or ask for help in the user list. This project is intended for reporting bugs in the Magnolia code itself.

"Recreating the anonymous user" wiki page should also provide you with a guide on how to recreate any role on public instance.

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