About Galaxy security

Galaxies are created without security. After creating a Galaxy, you can assign security to manage access to:

• IDE for configuring and managing objects and graphics

• Operations Control Management Console for performing maintenance and system administration functions

• Alarms, object data, and secured writes for a running ViewApp

• Credentials, which are linked to specific user groups and allow AVEVA OMI apps to connect to external resources that do not recognize Windows credentials. The security authentication mode must be set to OS Group based or OS User based in order to use credentials.

Each Galaxy in the Galaxy Repository manages its own security model. The security schema managed in a Galaxy is a three-level configuration model to create and maintain the following:

• Users assigned to roles

• Security roles granted system administration, configuration, and runtime (operational) permissions

• Security groups containing specific objects in a Galaxy

  

  The security matrix defines a cascading model of users associated with specific roles that are associated with specific security permissions that are associated with specific objects. User runtime permissions can vary from object to object, action to action, and process to process. The security icons associated with object attributes map directly to control points in the security model.