Setting up a Remote Authentication Server
The remote authentication server settings let the LogLogic LMI appliance participate in a centralized login authentication implementation.
TACACS, RADIUS, or Active Directory can be used by the appliance as authentication servers to verify user credentials. 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.
If you have configured multiple authentication servers, then the appliance attempts to authenticate a user using all servers one after another until the user is finally found on a server and authentication is successful. For example, If the authentication attempt fails on server1 (for example, the user does not have an account on server1), then the appliance attempts to authenticate the user on server2, and if necessary and applicable, on server3 and server4, and so on. An error is logged for each server on which the user is not found.
Prerequisites
- Add the appropriate users to the remote authentication server or ensure that their login IDs already exist.
- For TACACS or RADIUS:
- Add the IP addresses of the LogLogic LMI appliance 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.