Use Secured and Verified Writes

You can assign Secured Write or Verified Write security classification to a configurable attribute. These security classifications require authentication to perform run-time writes to the configured attribute. With authentication, users can write to such attributes by:

• Any assignment in a script that sets the value of the attribute, such as "A=B";

  where A references an attribute that is configured for Secured Write or Verified Write security classification.

• Any action on an animation graphic that alters the value of an attribute that has Signed Write or Verified Write security classification, such as a user input, a slider, an up/down button on a counter, or any other such actions.

• A script that uses the SignedWrite() function.

  For information about the SignedWrite() function, see Chapter 2, "QuickScript .NET Functions," in the Application Server Scripting Guide.

The operator and verifier provide credentials for authentication by entering a valid security account (domain name, user name, and password), or by using a Smart Card if a Smart Card reader is attached to the system.

Note: Smart Card authentication is not supported in multi-galaxy environments for read/write operations to remote galaxies.

Operators can write to attributes configured with Secured Write or Verified Write security classification even if another user is logged on. This does not affect the session of the logged-on user.

• The operator must have the Can Modify Operate Attributes operational permission to perform the Verified Write.

• The verifier must have the Can Verify Writes operational permission to confirm the Verified Write.

  For more information, see Set object security and About roles.

  Note: The Secured and Verified Write features work only when security is enabled on both the Galaxy and InTouch applications and do not work if either Galaxy or InTouch security is set to None.