Configuring the ActivID AAA Server
The AAA Server authentication solution consists of several elements that you must create and configure according to your required deployment.
Element | Description |
---|---|
Server | A server listens to authentication, authorization and accounting requests coming from the Access Controllers (such as routers, remote access servers, or firewalls) on the RADIUS and TACACS+ ports. |
Gate | A gate’s main role is to filter the requests according to the Access Controllers’ IP address. |
Profile |
A profile is a list of parameters (sets of attributes or attribute/value pairs) that determines user authentication and device policies – including policies on PINs, unlocking PINs, and authenticating.
|
Query |
A query is the primary way in which the AAA Server identifies your users and which device they are assigned. It enables the AAA Server to search your LDAP directory for the users that belong in the specified group. |
Group |
A user group is a logical grouping within the AAA Server that enables the AAA Server to efficiently manage user authentication. A group specifies how a set of users may authenticate to a resource(s) protected by the AAA Server, including which gate(s) they may use to access a resource. The AAA Server uses the LDAP query you’ve assigned to the group, as well as any additional filter you’ve defined for the group, to search your LDAP directory for the users that belong in the group. User groups in the AAA Server can mirror the user groups you have already created in your LDAP directory or not, as needed for authentication purposes. Users can belong to only one group in AAA. (Remember that a user group is only a logical grouping within the AAA Server. You continue to manage your users in your LDAP directory.) |
Device repository |
A device repository is a logical store of authentication devices (smart cards, tokens and USB keys). When you import pre-initialized devices, the AAA Server automatically stores authentication devices in the root device folder. You can create additional repositories in the root directory for storing devices, instead of the AAA Server automatically storing all devices in the root. Whether you have a large user database or a relatively small one, it’s easier to manage devices if you store them in an organized way. Some general categories to consider are:
|
Topics in this section
Each configuration task listed in this table consists of multiple actions.
The tasks are presented in the order in which you should handle them when you first configure the AAA Server.
After you are familiar with the AAA Server, you can handle the tasks in any order as long as prerequisites are met.