csmstr - Omega Engineering

USING THE SECURITY SYSTEM
SECURITY SETTINGS
to external data must be recorded, but where data internal to Crimson can be manipulated
without the need for such an audit trail.
ON-DEMAND LOGON
Crimson’s security system supports both conventional and on-demand logon. A conventional
logon can occur when a user interface element such as a pushbutton is used to activate the
Log On User action or to call the UserLogOn() function. On-demand logon occurs if the
operator attempts an action without sufficient access rights, and if a failed logon attempt has
not occurred within the same action. For example, a user may press a button that runs a
program to reset a number of values. As soon as the program attempts to change a value that
requires security access, the system will prompt for logon credentials. This method reduces
operator interaction, and produces a more responsive system.
MAINTENANCE ACCESS
The system also provides a facility called Maintenance Mode to allow the user inactivity
timeout to be overridden during system commissioning. This mode is activated if a display
page is marked as being accessible with the Maintenance Access right, and if the current user
has gained access to the page as a result of that right. Use of this mode avoids the need to
logon repeatedly when testing the system.
SECURITY SETTINGS
The security system settings are accessed via the Security Manager icon…
The available properties are as follows…
• The Inactivity Timeout property is used to indicate how much time must pass
without user input before the current user is automatically logged off. Too high a
value for this setting will produce an insecure system, while too low a value will
produce a system that is awkward for operators.
• The Clear Logon Name property is used to indicate whether or not the username
should be cleared before asking the operator to logon. If this setting is disabled,
the previous username will be displayed, and only the password will need to be
REVISION 6 PAGE 257