Using InTouch-Based Security

Security is based on operators authenticating themselves by entering a user name and password to log on to an InTouch application. You must assign user name, password, and access level for each operator.

When you create a new application, by default, the user name is set to Administrator with an access level of 9999, which allows access to all security commands. The default administrator password is wonderware. The maximum number of characters for a password is 29.

After you add a new user name to the security list and restart WindowMaker or WindowViewer, the default user name is automatically reset to None with an access level of 0, which prevents access to the Configure Users command in both WindowMaker and WindowViewer. However, the Administrator account and password remain and can still be used.

After an operator logs on to the application, access to any protected function is granted upon verification of the operator's password and access level against the value specified for the internal security tag linked to the function.

For Native and Modern applications, only users with Administrator privileges are allowed to open and edit applications in InTouch WindowMaker. If a user without administrator privileges attempts to launch InTouch WindowMaker, an error dialog box appears, informing users that they need administrative privileges to proceed. Users without administrative privileges can launch WindowMaker via ArchestrA IDE for Managed applications.

InTouch Security

InTouch security is a two-step process of first determining if the person attempting to use an application is recognized as a valid user. The second step determines what InTouch privileges have been granted to an authenticated user.

Key Points

• Security is based on operators authenticating themselves by entering a user name and password to log on to an InTouch application.
• You must assign an account name, password, and access level (0-9999) to each operator who will interact with an InTouch application.
• After an operator logs on to the application, access to any protected function is granted upon verification of the operator's password and access level against the value specified for the internal security tag linked to the function.
• You can also link a User Input - Discrete button to the $ConfigureUsers tag to allow an authorized operator with an access level of equal to or greater than 9000 to access the Configure Users dialog box to edit the security user name list.
• The $AccessLevel and $Operator system tags contain information of the currently logged-on user. If you want to restrict access to objects at run time, you can use these system tags in an animation link to prevent access.