SL 238 Fix access control

[sle3pyy]

This pull request introduces role-based access control for navigation links and routes in the web application. The main changes include adding roles metadata to navigation link definitions and implementing a centralized route access utility that checks user roles and features before allowing access to specific paths. Additionally, the root route component now enforces these access rules, redirecting unauthorized users to an appropriate default page.

Role-based navigation and route access:

• Added a roles property to each relevant entry in adminLinks and contentManagerLinks within web/src/config/navLinks.ts to specify which user roles are allowed to access each link. [1] [2] [3] [4]
• Created a new utility module web/src/lib/route-access.ts that builds route access policies from navigation links, normalizes user roles, and provides functions to check if a user can access a given path (canAccessPath) and to determine a default authorized path for a user (getDefaultAuthorizedPath).

Route access enforcement in root layout:

• Updated web/src/routes/__root.tsx to use the new route access utility, extracting user roles and features from the Keycloak token, checking access for the current path, and redirecting unauthorized users to their default authorized page. Also added a loading indicator while authentication is initializing.

[github-actions]

Lint Report

Result: ✖ 153 problems (140 errors, 13 warnings)

Download Full Lint Log
(Log available in the Artifacts section at the bottom of the page)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud