Setting up a Remote Authentication Server
The Remote Authentication Server settings let the LogLogic appliance participate in a centralized login authentication implementation.
TACACS, RADIUS, or Active Directory, can be used by the appliance as authentication servers to verify users' login and password. Active Directory also allows defining roles for groups of users, to which you can assign specific user privileges and access to specific log sources. You can define up to eight remote authentication servers.
Note: If you have multiple authentication servers configured, then the appliance attempts to authenticate a user using Remote Authentication Server 1. If the authentication attempt fails (for example, the user does not have an account on Remote Authentication Server 1, then the appliance attempts to authenticate the user on Remote Authentication Server 2, and if necessary and applicable, Remote Authentication Server 3 and 4, and so on.
Prerequisites
- Add the LogLogic appliance IP address(es) to your remote authentication server.
- If you have a failover configuration, you must add the private IP addresses from both appliances to the remote authentication server. For details, see Failover.
- Add the appropriate users to the remote authentication server or ensure that their logins already exist.
Procedure
- Select .
-
Select the appropriate radio button for the
Remote Authentication Servers:
- RADIUS—indicates to configure a remote server using the RADIUS protocol. RADIUS is used for access control only, not RADIUS accounting. The default port is 1812.
- TACACS—indicates to configure a remote server using the TACACS+ protocol. The default port is 49.
- Active Directory—indicates to configure a remote Active Directory server. The appliance roles associated with groups on the AD server are used for controlling appliance authentication, user privileges, and access to log sources. The default port is 389.
Copyright © Cloud Software Group, Inc. All rights reserved.