424
Enabling remote access with clientless VPN
Using roles to assign rules to users
5
Optionally, do one of the following:
■
To save your configuration and activate later, on the toolbar, click
Save
.
■
To activate your configuration now, on the toolbar, click
Activate
.
When prompted to save your changes, click
Yes
.
To add a rule to a rule set
1
In the SGMI, in the left pane, under Policy, click
Clientless VPN
.
2
In the right pane, on the Rule Sets tab, select the rule set to which you want to add a rule, and then
click
Properties
.
3
In the Rule Set Properties dialog box, on the General tab, click
Add
.
4
In the Rule/Rule Set Selection dialog box, select the rules or rule sets you want to add to the rule
set, and then click
OK
.
5
Click
OK
.
6
Optionally, do one of the following:
■
To save your configuration and activate later, on the toolbar, click
Save
.
■
To activate your configuration now, on the toolbar, click
Activate
.
When prompted to save your changes, click
Yes
.
7
After creating the rule set, you can add it to a clientless VPN role.
Related information
For further information related to this topic, see the following:
■
“Rule Set Properties—General tab”
■
“Clientless VPN Role Properties—General tab”
■
■
■
“Assigning a rule or rule set to a role”
Using roles to assign rules to users
Roles let administrators assign users access privileges and customized portal pages based on a user’s
function within an organization. The root role, from which all other roles inherit attributes, cannot be
modified or deleted.
Roles are arranged in a hierarchy that has a parent/child system of inheritance. The child role inherits
all the attributes of its parent and ancestor roles. This lets the administrator structure roles so that
privileges are assigned by function.
Each time an authentication server is configured on the security gateway, a role called DEFAULT is
automatically created and associated with it.
Note:
The security gateway has a root role that is the parent of all roles. Any rule that is assigned to the
root role is inherited by all other roles on the system. Initially, the root role contains no rules. You can
configure rules in the root role that you want to apply to all clientless VPN users.
For additional background information about roles, see the following topics:
■
“Role structure and inheritance”
■
Summary of Contents for Security 5600 Series, Security 5400 Series,Clientless VPN 4400 Series
Page 76: ...76 Managing administrative access Enabling SSH for command line access to the appliance...
Page 242: ...242 Defining your security environment Controlling full application inspection of traffic...
Page 243: ...243 Defining your security environment Controlling full application inspection of traffic...
Page 269: ...268 Limiting user access Authenticating using Out Of Band Authentication OOBA...
Page 373: ...372 Preventing attacks Enabling protection for logical network interfaces...
Page 509: ...508 Generating reports Upgrade reports...
Page 553: ...552 Advanced system settings Configuring advanced options...
Page 557: ...556 SSL server certificate management Installing a signed certificate...
Page 861: ...860 Index...