Allegro

Overview

Allegro UI is designed using the Aria CCP UI libraries and framework. Please note that the base for the library was what was provided and used in March 2025. Since then, CCP UI has evolved with introduction of more color schemes and UI visualizations. As a result, you might see some subtle differences. We intend to bridge that gap before or around the Release 67 deployment to production.

Accessing Allegro UI

This functionality is under development. The intent is that it will re-use the same framework that is currently used with CCP UI using the Key Cloak service that acts as an interface for oAuth2 authentication for the user or manage the SSO with an Identity manager service. There are two possibilities:

1. User is already logged in and has an active session with CCP UI or Admin UI and the user uses the link from the Admin UI or CCP UI to access Allegro UI. In this example, the user has an active session, and the Aria Allegro UI will not require re-login and will be provided with access to the Allegro UI
2. User session ends or the user logs in fresh with Allegro UI, the user will be provided with the same login screen as with Aria Admin UI and Aria CCP UI and a successful login would provide access to the Allegro UI.

How does Aria Allegro control the access levels for the users?

Allegro platform avoids re-inventing the entire User Management and creation of specific roles for Allegro UI. It manages the existing Aria framework to provide access to Allegro. All of this is seamless and behind the scenes covers the following:

1. A table of all Allegro permissions. This will continue to be managed with each release as more capabilities are added to the Allegro platform.
2. A Static configuration that provides the mapping of the permissions that are allowed in Aria Admin UI (subset that needs to be mapped) and the Allegro permissions.
3. Admin users will create roles in the Aria Admin UI as it is done today.
4. New users will be added using the same existing framework in Aria Admin UI.
5. For users trying to start a fresh new session, Allegro UI will guide them to the same login screen as used by the Aria Admin UI or the SSO login with the Identity manager setup for the deployment.
6. For existing users, the existing services will provide a token for the active session and that will be used with Allegro UI to grant access including the session timeout parameter.
7. Core Aria APIs at play with Allegro platform for access management,
   • getCurrentUser—Allegro UI calls Allegro core API which in turn calls the core Aria API to get the current user.
   • getUiAccountPrivileges—Allegro UI calls Allegro core API which in turn calls the core Aria API to get the current privileges for the user, overlay that with the mapping provided in point-2 and manage access according to the map data returned.
   • getUiProductCatalogPrivileges—Allegro UI calls Allegro core API which in turn calls the core Aria API to get the current privileges for the user for product catalog, overlay that with the mapping provided in point-2 and manage access according to the map data returned.
8. The UI will get the session timeout value and manage the session accordingly.

In the future, if required, a broader framework can be added which allows the following:

• Creation of Roles for Allegro permissions
• Creation of Role Groups to add different Roles into a Role Group
• Adding users into the platform
• Assigning Roles or Role Groups to a user.
• Creation of user groups with existing users.
• Managing multi-level approval with user groups for any functionality as required. For example, managing multi-level approval framework for Adjustments/Credit Memos based on reason code.

User Guide