Security

AVEVA Recipe Management uses web technologies for its deployment and controls access to Formula download and Recipe execution. Naturally, the need for a secure environment is paramount.

The first level of security is an authenticated access to AVEVA Recipe Management that uses AVEVA Identity Manager (AIM) as an identification service. When a user accesses the AVEVA Recipe Management Server from a web client, the AVEVA Identity Manager (AIM) validates the user credentials. AIM provides a valid token for the user which is used as a proof of authentication. AIM uses Secure Sockets Layer (SSL), token validation, and password authentication for enhanced security.

NOTE: If a Windows/Domain User is disabled or deleted in the OS or Domain, then their token may remain valid until they log out.

The second level of security decides what a particular user or group will be able to do once they have access to the AVEVA Recipe Management application. The administrator can grant specific users (or groups) privileges by assigning them to pre-configured security roles.

Within AVEVA Recipe Management, you use the Roles and Users/Groups pages to control the actions that each user or group can perform.

You must first create Roles, each with permission to carry out different actions. For example, you may want to create the role of Supervisor with access to all actions, such as the ability to edit Formulas and Equipment, and override checkouts. The role of Operator may have the permission to view information but not change anything.

After you have set up your roles, you can then assign them to your Users/Groups.

For information on Roles, refer to Working with Roles.

For information on Users and Groups, refer to Working with Users/Groups.