With the introduction of the new Angular-based portal, the user interface of One Identity Manager is undergoing a fundamental change.

In practice, it quickly becomes clear that the transition to the new One Identity Angular Portal affects far more than just the front end.

If the portal migration is analyzed too late, it quickly becomes apparent that the actual effort involved often only becomes clear during the migration itself. This can lead to time pressure, especially in environments with many existing customizations—a situation that can be avoided.

With the newer versions of One Identity Manager, the platform’s portal strategy is also changing. The existing Web Designer Portal is being gradually replaced by the Angular-based portal.

This becomes particularly relevant with version 9.3, in which the Angular Portal becomes the central user interface. Organizations that still rely heavily on the previous web portal should therefore assess early on which customizations and extensions need to be incorporated into the new One Identity Angular Portal.

Environments with a large number of custom web design extensions often face the task of analyzing existing portal components and, in some cases, reimplementing them—a process that often requires more effort than initially anticipated.

The new One Identity Angular Portal replaces the previous web portal as the strategic interface for One Identity Manager.

With the introduction of the Angular-based front end, One Identity aims to modernize the user interface from a technical standpoint and make it easier to maintain in the long term. The new architecture is based on the latest web technologies and enables improved performance, clearer user guidance, and more flexible future development of the platform.

At the same time, the transition to the new One Identity Angular Portal means that many existing customizations cannot be automatically carried over. Organizations with custom-extended portal interfaces or customized workflows must determine which extensions will continue to function and which will need to be adapted or reimplemented during the migration.

In many environments, existing customizations, self-service processes, and governance workflows are closely tied to the existing portal structure. As a result, several common challenges often arise during migration.

• Self-Service and Service Catalogs
  Service catalogs, approvals, and certifications are often closely tied to the structure of the existing web portal. When migrating to the Angular Portal, these processes must therefore be carefully reviewed.
  In particular, organizations with extensive self-service offerings must verify whether existing configurations will continue to function or need to be redesigned.
• Custom Portal Customizations
  Many organizations have expanded their web portals over the years, for example by adding UI components, custom forms, or tailored workflows.
  Since the Angular Portal is based on a new architecture, such extensions often cannot be ported over without modifications and may need to be reimplemented in part.
• User Experience for Business Units
  For businessusers, the portal is often the central entry point to identity and access management processes. Changes to navigation, structure, or forms have a direct impact on usage and acceptance. A successful portal migration therefore takes into account not only technical aspects but also the user experience for business units.
• Governance and Compliance
  Approval processes, certifications, and audit evidence must continue to function seamlessly even after migration. Organizations subject to regulatory requirements such as NIS2 or ISO 27001 should assess early on whether existing governance workflows can be accurately mapped in the new portal. An unprepared migration can create short-term compliance gaps that will become apparent during the next audit.

The specific impact of these factors depends heavily on the individual portal configuration and existing extensions. A structured analysis of the existing environment helps identify risks early on and prepare for the transition in a planned manner.

The transition to the Angular Portal affects several technical aspects of the One Identity Manager environment. In particular, organizations that have made extensive customizations to the existing Web Designer Portal need to assess how these customizations can be implemented in the new architecture.

Typical technical implications include, among other things:

• Existing web design extensions

• Custom portal components and UI customizations

• Self-service configurations and service catalogs

• Integration with API Server and Backend Services

• Changes to deployment and update processes

Many customizations not only need to be migrated but also partially reimplemented, as the Angular Portal is based on a fundamentally different architecture.

Many organizations do not begin to analyze the migration until specific problems arise. This is understandable, because as long as the existing portal is functioning, there is no obvious need to take action. In practice, however, it becomes clear that the later the existing environment is analyzed, the more difficult it becomes to plan the transition.

The Identity Team has already successfully supported the Angular portal migration. A recurring pattern in this process is that the effort required for customizations is initially underestimated, as many of them are no longer documented or known in day-to-day operations.

Typical analysis points:

• Existing portal customizations and their dependencies
• Assessment of Self-Service Processes for Migrability
• The Impact of UX on Business Units
• Review of Governance Workflows
• Migration Roadmap with Realistic Prioritization

On this basis, the transition to the One Identity Angular Portal can be realistically planned, from prioritizing individual customizations to the phased migration of self-service processes and governance workflows.

The transition to the One Identity Angular Portal is an important step in the platform’s ongoing development. At the same time, experience shows that the migration involves much more than just a change in the user interface.

Existing configurations, self-service processes, and governance workflows often need to be reviewed and, in some cases, reimplemented. Organizations that tackle the transition early on and in a structured manner can reduce risks and make the transition significantly more efficient.