Allow Role Hierarchy in the SAML app

User Story

As a backend SSO user,
I want to be able to define and pass roles with hierarchical naming (e.g., Designer.Manager, Developer.Manager)
So that I can reuse role names under different parent contexts while maintaining distinct role identities.
This will allow SAML to correctly assign and map roles based on both their name and their parent group or category.

Example:

Designer.Manager – Represents a Manager within the Designer group

Developer.Manager – Represents a Manager within the Developer group

Despite sharing the same sub-role (Manager), the prefix (Designer, Developer) ensures these are treated as separate roles in SSO role mapping.

Acceptance Criteria

Allow for role hierarchy to be accepted in the assertion so it matches the hierarchy setup in the dotCMS backend

Proposed Objective

Customer Support

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.freshdesk.com/a/tickets/30780

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Review the SAML assertion role handling and the dotCMS backend role hierarchy described in the issue, using support ticket 30780 for additional context. Define completion as accepting hierarchical role names such as Designer.Manager and Developer.Manager and matching them to the corresponding backend hierarchy during role mapping.