feat: role-based feature visibility — App Profiles + Platform Profiles (backend)

[ppatel9703]

Summary

Adds a Role-Based Feature Visibility system to SEMOSS with two independent subsystems:

• App Profiles — flat per-portal feature gating with profiles and delegated manager access
• Platform Profiles — platform-wide feature gating for controlling shell/nav visibility globally

Both systems are backed by new security DB tables, fully integrated into the SEMOSS OWL/metamodel, and exposed via Pixel reactors.

---

What Changed

New Tables (Security DB)

App Profile system — 5 tables (group/subgroup tables removed in this branch):

Table	Purpose
APP_FEATURE	Feature catalogue per app (featureId, featureKey, appId)
APP_PROFILE	Named flat profile per app (isDefault flag; IS_GROUP column retained but always false)
APP_PROFILE_FEATURE	Feature enabled/disabled state per profile
APP_USER_PROFILE	Explicit user → profile assignment
APP_PROFILE_MANAGER	Non-admin users delegated manage rights for an app

Platform Profile system — 3 tables:

Table	Purpose
PLATFORM_PROFILE	Named platform-wide profile
PLATFORM_PROFILE_FEATURE	Feature key/enabled state per platform profile
PLATFORM_USER_PROFILE	User → platform profile assignment

Tables are created in AbstractSecurityUtils on startup (idempotent CREATE IF NOT EXISTS) and registered in SecurityOwlCreator with full OWL relations.

---

App Profile Reactors — 21 reactors in src/prerna/reactor/appprofile/

feature/

• CreateAppFeature, UpdateAppFeature, DeleteAppFeature, GetAppFeatures
• CheckAppFeature, CheckFeature (alias), GetAppUserFeatures

profile/

• CreateAppProfile, UpdateAppProfile, DeleteAppProfile, GetAppProfiles
• SetAppProfileFeature, GetAppProfileFeatures, GetAppProfileUsers

manager/

• AddAppProfileManager, RemoveAppProfileManager, GetAppProfileManagers

user/

• AssignAppUserProfile, RemoveAppUserProfile
• GetUserAppProfiles, GetUserProfile (legacy alias)

Removed in this branch (group/subgroup model):

• subgroup/ — 9 reactors deleted: CreateAppSubgroup, UpdateAppSubgroup, DeleteAppSubgroup, GetAppSubgroups, SetAppSubgroupFeature, GetAppSubgroupFeatures, GetAppSubgroupUsers, AssignAppUserSubgroup, RemoveAppUserSubgroup

---

Platform Profile Reactors — 10 reactors in src/prerna/reactor/platformprofile/

• CreatePlatformProfile, UpdatePlatformProfile, DeletePlatformProfile, GetPlatformProfiles
• SetPlatformFeature, GetPlatformFeatures
• AssignUserPlatformProfile, RemoveUserPlatformProfile, GetPlatformProfileUsers
• GetUserPlatformFeatures

---

Supporting Changes

File	Change
AbstractSecurityUtils.java	Creates all new tables on startup
SecurityOwlCreator.java	Registers tables + OWL relations to PROJECT, SMSS_USER
ReactorKeysEnum.java	Added FEATURE_KEY, ENABLED, IS_DEFAULT, IS_GROUP, PROFILE_ID keys
SystemEngineRegistry.java	Added prerna.reactor.appprofile to security DB allowed prefix set

---

Key Design Decisions

Flat Profile Model (group/subgroup removed)

The original design included group-type profiles with subgroups, which caused four concrete bugs:

1. setProfileFeature threw for group profiles but the UI rendered toggles anyway
2. userCount was wrong for group profiles (counted APP_USER_PROFILE not APP_USER_SUBGROUP)
3. Direct user assignment to a group profile created a silent feature dead-end
4. Delegated managers could see subgroup write controls that would fail at the backend

All profiles are now flat. Feature states are set directly on the profile. IS_GROUP column is retained in the DB schema for continuity but is always written as false and never read.

Feature Resolution Order (App Profiles)

1. Explicit profile assignment → use that profile's feature states
2. Default profile (IS_DEFAULT=true) as fallback
3. All false if no assignment and no default

Access Control

• App profile writes: admin OR user in APP_PROFILE_MANAGER for that app
• Platform profile writes: admin only
• Evaluation reads (CheckAppFeature, GetAppUserFeatures, GetUserAppProfiles): any authenticated user, returns only their own data — canEvaluateFeatures guard removed

getUserFeatures return type

AppProfileUtils.getUserFeatures now returns Map<String, Boolean> (featureKey → true/false for every feature in the app's catalogue). Previously returned Map<String, Object> with nested feature metadata.

getExplicitUserProfiles — two-query in-memory join

OWL join traversal between APP_USER_PROFILE and APP_PROFILE was unreliable. Replaced with two single-table queries joined in memory.

Duplicate profile name guard

createProfile rejects duplicate names per app at the application layer before INSERT.

Bulk Assignment

AssignAppUserProfile accepts a list of user IDs. Returns { assigned, skipped, errors } — each user processed independently.

Platform Profile — replace semantics

A user can be in at most one platform profile. Assigning to a new profile deletes the prior assignment first. App profiles are additive (a user can be in multiple).

---

How to Test

# Create feature + profile
CreateAppFeature(app=["<appId>"], featureKey=["dark-mode"]);
CreateAppProfile(app=["<appId>"], name=["Standard"], isDefault=["true"]);

# Set feature state
SetAppProfileFeature(app=["<appId>"], profileId=["<profileId>"], featureId=["<featureId>"], enabled=["true"]);

# Bulk assign users
AssignAppUserProfile(app=["<appId>"], userId=["<user1>", "<user2>"], profileId=["<profileId>"]);
# Returns { assigned: [user1, user2], skipped: [], errors: {} }

# Evaluate features
GetAppUserFeatures(app=["<appId>"]);
# Returns { "dark-mode": true }

CheckAppFeature(app=["<appId>"], featureKey=["dark-mode"]);
# Returns true

# Delegate manager
AddAppProfileManager(app=["<appId>"], userId=["<user1>"]);

---

Checklist

• No protected files committed (RDF_Map.prop, social.properties, db/, server.xml)
• All new tables created idempotently in AbstractSecurityUtils
• OWL relations registered in SecurityOwlCreator
• SystemEngineRegistry allowlist updated for new package prefix
• Write operations gated on admin or manager check
• Evaluation reads open to any authenticated user (canEvaluateFeatures guard removed)
• All reads use QueryColumnSelector aliases + QueryExecutionUtility (no raw JDBC for reads)
• Bulk assign: each user processed independently, non-empty list validated
• Group/subgroup model fully removed — 9 reactor files deleted, all subgroup methods removed from AppProfileUtils
• Platform profile one-per-user semantics enforced (DELETE before INSERT on reassign)
• IS_GROUP column preserved in schema for continuity, always written false, never read

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.