About UAA Groups

A UAA group is created for a specific type of users who will likely perform the same type of activities.

If you have groups in a remote UAA service, you can use them with Historian using the UAA LDAP Integration tool. This section describes how to map the groups in the remote UAA service with Historian UAA groups. By default, Historian contains the following UAA groups:
  • historian_visualization.admin: Provides access to Trend Client and the Web Admin console.
  • historian_visualization.user: Allows access to Trend Client.
  • historian_rest_api.read: Provides read access to public REST API.
  • historian_rest_api.write: Provides write access to public REST API.
  • historian_rest_api.admin: Provides read/write access to public REST API.
  • historian_enterprise.admin: Provides read/write access to Configuration Hub APIs.
Note: Instead of mapping the groups, you can choose to map individual users with Historian users. For instructions, refer to Using the UAA Config Tool.

Workflow

  1. Provide the details of the remote UAA service while installing Web-based Clients.
  2. Connect to the remote UAA service.
  3. Map the UAA groups with that of the Historian UAA instance. You can map the groups in LDAP and LDAPS (LDAP via SSL) as well.
    Tip: To create UAA groups and users, refer to