01.12.2012 Views

system

system

system

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.

HIMax System 6 User Management<br />

6 User Management<br />

SILworX can set up and maintain an own user management scheme for each project and<br />

controller.<br />

6.1 User Management for SILworX Projects<br />

A PADT user management scheme for administering the access to the project can be<br />

added to every SILworX project.<br />

If no PADT user management scheme exists, any user can open and modify the project. If<br />

a user management scheme has been defined for a project, only authorized users can<br />

open the project. Only users with the corresponding rights can modify the projects. The following<br />

authorization types exist.<br />

Type Description<br />

Safety Administrator<br />

(Sec Adm)<br />

Safety administrators can modify the user management scheme:<br />

setting up, deleting, changing the PADT user management<br />

scheme, and the user accounts and user groups, setting up the<br />

default user account.<br />

Furthermore, they can perform all SILworX functions.<br />

Read and Write (R/W) All SILworX functions, except for the user management<br />

Read only (RO) Read-only access, i.e., the users may not change or archive the<br />

projects.<br />

Table 25: Authorization Types for the PADT User Management Scheme<br />

The user management scheme allocates the rights to the user groups. The user groups allocates<br />

the rights to the user accounts assigned to it.<br />

Characteristics of user groups:<br />

� The name must be unique within the project and must contain 1...31 characters.<br />

� A user group is assigned an authorization type.<br />

� A user group may be assigned an arbitrary number of user accounts.<br />

� A project may contain up to 100 user groups.<br />

� If the name of a user group is changed, it might happen that the controllers can no<br />

longer be loaded by performing a reload.<br />

Characteristics of user accounts:<br />

� The name must be unique within the project and must contain 1...31 characters.<br />

� A user account is assigned a user group.<br />

� A project may contain up to 1000 user accounts.<br />

� A user account can be the project default user<br />

6.2 User Management for the Controller<br />

The user management for a controller (PES user management) is used to protect the HI-<br />

Max controller against unauthorized access and actions. The user and its access rights are<br />

part of the project; they are defined with SILworX and loaded into the processor module.<br />

The user management is used to set and manage the access rights to a controller for up to<br />

ten users. The access rights are stored in the controller and remain valid also after switching<br />

off the operating voltage.<br />

Each user account is composed of name, password and access right. The user data can be<br />

used to log in once a download has been performed to load the project into the controller.<br />

The user accounts of a controller can also be used for the corresponding remote I/Os.<br />

Users log in to a controller using their user name and password.<br />

HI 801 001 E Rev. 3.00 Page 61 of 104

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

Saved successfully!

Ooh no, something went wrong!