Belkin OmniView manual 1f. User Search Sub-Filter, 1g. Active Directory Domain, 2a. Server

4-5 Device Settings

Menu Options

1f. User Search Sub-Filter

Here you can refine the search for users that should be known to the RIPM.

1g. Active Directory Domain

This option represents the active directory domain that is configured in the Microsoft Active Directory server. This option is only valid if you have chosen a Microsoft Active Directory as the LDAP server type.

2.Remote Authentication Dial In User Service (RADIUS)

RADIUS is a protocol specified by the Internet Engineering Task Force (IETF) working group. There are two specifications that make up the RADIUS protocol suite: authentication and accounting. These specifications aim to centralize authentication, configuration, and accounting for dial-in services to an independent server. The RADIUS protocol exists in several implementations such as free RADIUS, open-RADIUS, or RADIUS on UNIX systems. The RADIUS protocol is well specified and tested. We can give a recommendation for all products listed above, especially for the free RADIUS implementation.

Note: Currently, we do not support challenge/response. An “Access Challenge” response is seen and evaluated as an “Access Reject”.

To access a remote device using the RADIUS protocol, you must log in. You will be asked to specify your username and password. The RADIUS server will read your input data (Authentication), and the RIPM will look for your profile (Authorization). The profile defines (or limits) your actions and may differ depending on your specific situation. If there is no such profile, your access via RADIUS will be refused. In terms of the remote-activity mechanism, the login via RADIUS works like the Remote Console. If there is no activity for half an hour, your connection to the RIPM will be interrupted and closed.

2a. Server

Enter either the IP address or the host name of the RADIUS server to be connected. If you are using the host name, DNS must be configured and enabled.

2b. Shared Secret

A shared secret is a text string that serves as a password between the RADIUS client and RADIUS server. The RIPM serves as a RADIUS client. A shared secret is used to verify that RADIUS messages are sent by a RADIUS-enabled device that is configured with the same shared secret and to verify that the RADIUS message has not been modified in transit (i.e., to verify message integrity). For the shared secret, you can use any standard alphanumeric and special characters. A shared secret may consist of up to 128 characters and may contain both lowercase and uppercase letters (A–Z, a–z), numerals (0–9), and other symbols (characters not defined as letters or numerals), such as exclamation points (“ ! ”) or asterisks (“ * ”).

2c. Authentication Port

The port the RADIUS server listens to for authentication requests. The default value is #1812.

65