NetLinx Security
User Name
A user name is a valid character string (4 - 20
Group Name
A group name is a valid character string (4 - 20
Password
A password is a valid character string (4 - 20
Access Rights
Each of the features of the NetLinx master has security procedures defined for them. The access right for a particular feature determines if the user / group is to have access to the feature (make use of the feature).
Directory Associations
A Directory Association is a path that defines the directories and/or files that a particular user or group can access via the HTTP (Web) Server on the NetLinx master. This character string can range from 1 to 128
A single '/' is sufficient to grant access to all files and directories in the user directory and it's sub- directory. The '*' wildcard can also be added to enable access to all files. All entries should start with a '/'. Here are some examples of valid entries:
Path | Notes |
/ | Enables access to the user directory and all files and subdi- |
| rectories in the user directory. |
/* | Enables access to the user directory and all files and subdi- |
| rectories in the user directory. |
/user1 | If user1 is a file in the user directory, only the file is granted |
| access. If user1 is a subdirectory of the user directory, all |
| files in the user1 and its |
/user1/ | user1 is a subdirectory of the user directory. All files in the |
| user1 and its |
/Room1/iWebControlPages/* | /Room1/iWebControlPages is a subdirectory and all files |
| and its subdirectories are granted access. |
/results.txt | results.txt is a file in the user directory and access is |
| granted to that file. |
By default, all accounts that enable HTTP Access are given a '/*' Directory Association if no other Directory Association has been assigned to the account.
| 26 | NetLinx Master Cards and Modules |
|
|
|