You can configure AuthMinder for one of the following roles:
The following steps summarize the process that takes place when AuthMinder is configured as a RADIUS server:
1. A RADIUS client sends an authentication request to AuthMinder.
2. AuthMinder authenticates the user and sends the authentication response.
The following steps summarize the process that takes place when AuthMinder is configured as a proxy server for a RADIUS server:
1. A RADIUS client sends an authentication request to AuthMinder.
2. Based on the authentication policy configured in AuthMinder, the request may be forwarded to the RADIUS server. For example, you can configure AuthMinder to forward authentication requests to the RADIUS server when the user or user’s credential is not found in the AuthMinder database.
In some scenarios, you may want to configure AuthMinder as both a RADIUS server and as a proxy to a RADIUS server. For example, suppose you have recently installed AuthMinder. Some users have been migrated to AuthMinder, and the remaining users are still on the existing RADIUS solution. In this case, you configure AuthMinder as both a RADIUS server and as a proxy to a RADIUS server. Now, RADIUS authentication requests from users that have been migrated to AuthMinder are handled by AuthMinder. For all other users, AuthMinder forwards the RADIUS authentication requests to the existing RADIUS server because the users or users’ credentials are not found in the AuthMinder database.
This scenario explains the procedure to configure AuthMinder for RADIUS. The following diagram outlines the steps of this procedure:
Perform the following tasks to configure AuthMinder as a RADIUS server or as a proxy server for a RADIUS server:
Copyright © 2013 CA Technologies.
All rights reserved.
|
|