About User Authentication and Authorization (UAA)

In Historian, user authentication is handled using User Account and Authentication (UAA). UAA provides identity-based security for applications and APIs. It supports open standards for authentication and authorization, including Oauth2.

When a user is created, modified, or deleted in Historian, the associated user account is being created, modified, or deleted in the UAA instance, respectively.

Note: This is done in the backend automatically. Therefore, most users will not need knowledge on UAA to perform basic user management, except when additional configuration is required.

To use UAA, you can choose among the following options:

Creating a new instance of UAA: Use this option if you are not currently using a UAA instance.
Using an existing UAA: Use this option if you are currently using UAA that contains users and groups. The users in the existing UAA instance can then use Historian Web-based Clients. You can then manage these users in Historian Web-based Clients. To use an existing instance of UAA, you must provide the details while installing Historian Web-based Clients.