PingIDM

User interfaces

To use any IDM UI in a production environment, it must only be accessed in an HTTPS context. You can accomplish this using a separate server (such as an SSL-terminating reverse proxy) or directly configuring the web server hosting the UI files to support HTTPS. The specific implementation choice for using HTTPS is outside the scope of this documentation.

The admin UI provides a graphical interface for most aspects of the IDM configuration. If IDM is installed on the local system, access the admin UI at https://localhost:8443/admin.

You can use the browser-based admin UI for configuring and managing users and roles, setting up synchronization between resources, configuring connectors, and more.

End-user UI

The IDM end-user UI provides role-based access to specific tasks and allows users to manage certain aspects of their own accounts. You can download it as a separate artifact from the Backstage download site and serve it from either:

  • A standalone Nginx server

  • A Docker container built from the included Dockerfile

Learn more in Install the end-user UI.

After installation, you can access the IDM end-user UI at the Nginx host and port (for example, http://localhost:8083).

Browser ad blocker extensions can inadvertently block some UI functionality, particularly if your configuration includes strings such as ad. For example, a connection to an Active Directory server might be configured at the endpoint system/ad. To avoid problems related to blocked UI functionality, remove the extension, or configure a safelist to ensure access to the targeted endpoints.