05.05.2014 Views

csmstr - Omega Engineering

csmstr - Omega Engineering

csmstr - Omega Engineering

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

USING THE SECURITY SYSTEM<br />

SECURITY BASICS<br />

USING THE SECURITY SYSTEM<br />

Crimson contains powerful features to allow you to define which operators have access to<br />

which display pages, and limit those operators who are able to make changes to sensitive<br />

data. The software also contains a security logging facility that can be used to record changes<br />

to data values indicating when the change occurred, and by whom it was performed.<br />

SECURITY BASICS<br />

The follow sections details some of the basic concepts used by the security system.<br />

OBJECT-BASED SECURITY<br />

Crimson’s security system is object-based. This means that security characteristics are applied<br />

to a display page or to a tag, and not to the user interface element that accesses the page or<br />

makes a change to the tag. The alternative subject-based approach typically means that you<br />

have to be careful to apply security settings to every single user interface element that might<br />

change restricted data. Crimson’s approach avoids this duplication and ensures that once you<br />

have decided to protect a tag, it will remain protected throughout your database.<br />

NAMED USERS<br />

Crimson supports the ability to create any number of users, each of whom will have a<br />

username, a real name and a password. The username is a case-insensitive string with no<br />

embedded spaces that is used to identify the user when logging on, while the real name is<br />

typically a longer string that is used within logon files to record the human-readable identity<br />

of the user making a change. Note that you are free to use these fields in other ways if it suits<br />

your application: You may, for example, create users that represent groups of individuals or<br />

perhaps roles, such as Operators, Supervisors and Managers. You may also decide to use the<br />

real name to hold an item such as a clock number to tie user identities into your MRP system.<br />

USER RIGHTS<br />

Each user is granted zero or more access rights. A user with no rights can access those objects<br />

that merely require the identity of the user to be recorded, whereas users with more rights can<br />

REVISION 6 PAGE 255

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!