Historian security components and their privileges – Rockwell Automation FactoryTalk Historian SE 4.0 Installation and Configuration Guide User Manual

Page 65

Advertising
background image

Configuring FactoryTalk Historian Chapter 5

Rockwell Automation Publication HSE-IN025A-EN-E–September 2013

65

The connection between the Windows users and/or groups and the
Historian server security users is established through mappings. If
you want to grant a Windows user or group access to a Historian
server resource (such as a point or a module), you need to create on
the Historian server mappings between the Windows users and/or
groups and relevant Historian server users or groups. In this way, the
Windows users and/or groups adopt the permissions from the

Historian users to which they are mapped. This is the safest,
quickest and most convenient way of distributing the Historian
server privileges.

You can manage the Historian server security with the System
Management Tools.

See the following sections to learn more about the Historian server
security model:

• Historian Security Components and Their Privileges (page

65)

• Managing Historian Security Components (page 69)
• Creating Security Mappings (page 71)
• Managing Security of the Historian Server Database (page 73)

The following components constitute the Historian security model:

Identities

Users

Groups

PIEngineers

FTHEngineer

FTHEngineers

PIOperators

FTHOperator

FTHOperators

PISupervisors

FTHSupervisor

FTHSupervisors

PIWorld

pidemo

FTHAdministrators

piadmin

piusers

The descriptions and privileges of the security components are
presented in the following tables:

Historian Security
Components and Their
Privileges

Advertising