8.2. Authentication Setup
8.2.1. Setup Summary
The following list summarizes the steps for User Authentication setup with NetDefendOS:
•
Set up a database of users, each with a username/password combination. This can exist locally in
a NetDefendOS User DB object, or remotely on a RADIUS server and will be designated as the
Authentication Source. Membership of an Authentication Group can optionally be specified for
each user.
•
Define an Authentication Rule which describes which traffic is to be authenticated and which
Authentication Source will be used. These are described further in Section 8.2.5,
“Authentication Rules”.
•
If required, define an IP object for the IP addresses of the clients that will be authenticated. This
can be associated directly with an authentication rule as the originator IP or can be associate
with an Authentication Group.
•
Set up IP rules to allow the authentication to take place and also to allow access to resources by
the clients belonging to the IP object set up in the previous step.
The following sections describe the components of these steps in detail.
Authentication Sources
The database that an Authentication Rule uses to check a user's username/password combination can
be one of the following types:
•
The local user database internal to NetDefendOS.
•
A RADIUS server which is external to the D-Link Firewall.
•
An LDAP Server which is also external to the D-Link Firewall.
8.2.2. The Local Database
The Local User Database is a built-in registry inside NetDefendOS which contains the profiles of
authorized users and user groups. Usernames and passwords can be entered into this database, and
users with the same privileges can be collected together into groups to make administration easier.
There are two default user groups, the administrators group and the auditors group. Users that are
members of the administrators group are allowed to change the NetDefendOS configuration, while
users that belong to the auditors group are only allowed to view the configuration. Press the buttons
under the Groups edit box to grant these group memberships to a user.
8.2.3. External RADIUS Servers
Reasons for External Servers
In a larger network topology with a larger administration workload, it is often preferable to have a
central authentication database on a dedicated server. When there is more than one D-Link Firewall
in the network and thousands of users, maintaining separate authentication databases on each device
becomes problematic. Instead, an external authentication server can validate username/password
combinations by responding to requests from NetDefendOS. To provide this, NetDefendOS
supports the Remote Authentication Dial-in User Service (RADIUS) protocol.
8.2. Authentication Setup
Chapter 8. User Authentication
304
Summary of Contents for 800 - DFL 800 - Security Appliance
Page 24: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 24 ...
Page 69: ...2 6 4 Restore to Factory Defaults Chapter 2 Management and Maintenance 69 ...
Page 121: ...3 9 DNS Chapter 3 Fundamentals 121 ...
Page 181: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 181 ...
Page 192: ...5 5 IP Pools Chapter 5 DHCP Services 192 ...
Page 282: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 282 ...
Page 300: ...mechanism 7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 300 ...
Page 301: ...7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 301 ...
Page 318: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 318 ...
Page 322: ...ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 322 ...
Page 377: ...Management Interface Failure with VPN Chapter 9 VPN 377 ...
Page 408: ...10 4 6 SLB_SAT Rules Chapter 10 Traffic Management 408 ...
Page 419: ...11 5 HA Advanced Settings Chapter 11 High Availability 419 ...
Page 426: ...12 3 5 Limitations Chapter 12 ZoneDefense 426 ...
Page 449: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 449 ...