Legacy productThe WF1740 described here is an old product and no longer supplied. Please see details of current FireBrick products.

FireBrick 105
Manuals
Home

Users

The FireBrick uses a username/password system to manage security. There can be a number of different users of the system, and each can have their own access permissions. One user is special, the nobody user, which defines the permissions before you are actually logged in as anyone else.

Login

If you are not logged in as a specific user, you can select Login on the top left of the screen, and enter a user name and password. If you are logged in then you have a link to Logout instead. To change to another user, log out and then log in again.

User settings

Name	Allows you to give the user a full name for your reference
Security	Sets the security level of this user and so defines who can view or edit the users details
Profile	Defines the profile when the user can log in or use the FireBrick.
Login	The login name, i.e. what is typed in to the login box
Allow from	You can select one or more interfaces from which this user is allowed to log in.
Page colour	You can select the background colour for the FireBrick configuration pages when that user is logged in. This can be useful if you manage several different FireBricks as you can give each a different colour.
Timeout	This defines the timeout, in minutes, after which the user is automatically logged out if they have no accessed a page for that long.
Lines	This defines how many lines are shown on each page of entries in the administration pages.
View rights	There are 8 security levels, 1 to 8, and the check boxes define which security levels this user can view. This allows the user to see all details of any items at any level that is ticked, but not necessarily make changes.
Edit rights	This defines which security levels the user has permission to change. Any items with a level that is ticked can be changed by the this user.

Technical Reference

It is important to also ensure that the nobody user also has permisions from at least the same interfaces as any specific user otherwise that user could not get to the login screen in order to login (as they are the nobody user until they have actually logged in). E.g. to allow WAN address to a user, also allow WAN access for the nobody user.
It is not sensible to tick an edit right without a corresponding view right.