This tab allows you to view the current and assign a new RADIUS payload to the Defender Security Server object.
On this tab, you can use the following elements:
Click the Select button to select the user for whom you want to view the RADIUS payload that will apply.
The DSS list shows the Defender Security Server that is currently selected for the user. If necessary, select any other Defender Security Server.
The DAN list shows the Access Node that is currently selected for the user. If necessary, select any other Access Node.
The Effective Payload area displays the details of the RADIUS payload that will be effective when the selected user authenticates via Defender.
Remote Access Dial in User Service (RADIUS) is an access-control protocol that verifies and authenticates users based on challenge-response method. This protocol allows a computer to verify your identity, find out what you are allowed to access, and then tell you all of this.
The RADIUS protocol is built around the AAA concept, which stands for authentication (the process of verifying identity), authorization (the process of defining what you are allowed to do), and accounting (the process of monitoring logging statistics and usage information).
The purpose of RADIUS payload is to have the Defender Security Server send information back to the NAS device for reasons such as extra security or for accounting or other reasons specific to the NAS.
To create a RADIUS payload object
A wizard starts.
The next table lists the attributes you can assign to a RADIUS payload. The RADIUS payload will return these attributes after user’s access to the resource has been approved. For instructions on how to create a RADIUS payload, see Creating a RADIUS payload object.
Attribute |
Description |
06: Service-Type |
Specifies the type of service the user has requested or the type of service to be provided. This attribute can take one of the following values:
|
07: Framed-Protocol |
Specifies the framing to be used for framed access. This attribute can take one of the following values:
|
08: Framed-IP-Address |
Specifies the address to be configured for the user. This attribute can take one of the following values:
|
09: Framed-IP-Netmask |
Specifies the IP netmask to be configured for the user when the user is a router to a network. |
10: Framed-Routing |
Specifies the routing method for the user when the user is a router to a network. This attribute can take one of the following values:
|
11: Filter-Id |
Specifies the name of the filter list for particular user. The value of this attribute can include individual groups or all groups of which the user is a member. The default value is all groups. When the user has been successfully authenticated by the Defender Security Server, groups that include the authenticated user’s ID are returned to the NAS. |
12: Framed-MTU |
Specifies the maximum transmission unit (MTU) to be configured for the user when it is not negotiated by some other means such as PPP. |
13: Framed-Compression |
Specifies a compression protocol to be used for the link. This attribute can take one of the following values:
|
14: Login-IP-Host |
Specifies the system with which to connect the user, when the Login-Service attribute is included. This attribute can take one of the following values:
|
25: Class |
Available to be sent by the server to the client in an Access-Accept and should be sent unmodified by the client to the accounting server as part of the Accounting-Request packet if accounting is supported. The value of this attribute can include individual groups or all groups of which the user is a member. When the user has been successfully authenticated by the Defender Security Server, groups that include the authenticated user’s ID are returned to the NAS that initiated the authentication request. |
26: Vendor Specific |
Specifies a method for communicating vendor-specific information between Network Access Servers and RADIUS servers. This attribute encapsulates vendor-specific attributes, allowing vendors to support their own extended attributes otherwise not suitable for general use. |
Custom |
Allows you to specify a custom attribute by attribute ID. |
For users to authenticate and access resources protected with Defender, you need to configure and assign security tokens supported by Defender to them. Defender can work with a number of security tokens, which include native Defender tokens and third-party tokens.
The native Defender tokens include the following:
Third-party security tokens supported by Defender include Authy, DIGIPASS GO, Google Authenticator, Symantec VIP credentials, and YubiKey.
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center