[MGNLUI-6450] Consider using JCR datasource for users Created: 09/Dec/20  Updated: 24/Mar/23

Status: Open
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.3
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLUI-6449 Actions 'Show permissions' missing Open
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
Epic Link: Security maintenance

 Description   

The PoC was using user manager API to work with users, no tree structure (no folders, no move action).

Using plain JCR datasource (same as the old app) seems to be the easiest way to support this again.

 

As consequence:

  • filtering by roles/groups/realms will be gone.
  • no external users

 

 


Generated at Mon Feb 12 09:36:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.