NetLinx Security within the Web Server

The following table lists the NetLinx System Security options that can be granted or denied by an administrator or other authorized user:

Security Features

Feature

Description

 

 

System Level:

Provides an authorized user with the ability to alter the current

 

security options of the system assigned to the target Master.

 

 

Group Level:

Provides an authorized user with the ability to assign and alter

 

group properties such as creating, modifying, or deleting a

 

group’s rights, and also allows for the definition of the files/

 

directories accessible by a particular group.

 

• Any properties possessed by a group (access rights/directory

 

associations, etc.) are inherited by all members of that group.

 

 

User Level:

Provides an authorized user with the ability to assign and alter

 

user properties such as creating, modifying, or deleting a users’

 

communication rights, and defining the files/directories

 

accessible by a particular user.

 

 

Enabling the Master Security option after the groups, users, and passwords have been set up is highly recommended. If not, when the user accesses the Master from within another session, the default administrator username and password must be used for access.

Security - System Level Security page

To access this page, click the Security Level link from within the Security section of the Navigation frame. This page is strictly used to guarantee that a valid username and password is entered prior to gaining access to the listed features and options.

If the Master Security option is not selected, the Master is completely open and can be modified by anyone accessing the target Master via the web server’s UI.

The options on the NetLinx Master Security page (FIG. 36) are only accessible and configurable if the Master Security checkbox is selected. The Master Security checkbox selection toggles the appearance of the NetLinx Master security options and makes them accessible. Enabling an option on this page requires that a user enter a valid username and password before they are granted access to the specific feature. Some examples are:

Requiring verification before accessing the Master - HTTP Access must be enabled.

Requiring verification before altering a current Master security setting - Master Security and Configuration must be enabled.

Requiring verification from a communicating AMX software (such as NetLinx Studio v 2.4 or TPD4 v 2.5) before accepting communication for file/firmware transfers, the Configuration, ICSP Connectivity and Require Encryption options must be enabled.

NI-3101-SIG Signature Series NetLinx Integrated Controller

39

 

 

Page 49
Image 49
AMX NI-3101-SIG manual Security System Level Security, Security Features, Accessible by a particular user