11-5
User Guide for Cisco Secure ACS for Windows Server
78-14696-01, Version 3.1
Chapter 11 Working with User Databases
About External User Databases
•
RSA SecureID token servers
•
RADIUS-based token servers, including:
–
ActivCard token servers
–
CRYPTOCard token servers
–
Vasco token servers
–
PassGo token servers
–
SafeWord token servers
–
Generic RADIUS token servers
For Cisco Secure ACS to interact with an external user database,
Cisco Secure ACS requires an API for third-party authentication source. The
Cisco Secure ACS communicates with the external user database using the API.
For Windows NT/2000 and Generic LDAP, the program interface for the external
authentication is local to Cisco Secure ACS. In these cases, no further
components are required.
In the case of Novell NDS authentication, Novell Requestor must be installed on
the same Windows server as Cisco Secure ACS.
In the case of ODBC authentication sources, in addition to the Windows ODBC
interface, the third-party ODBC driver must be installed on the Cisco Secure ACS
Windows server.
To communicate with an RSA token server, you must have installed software
components provided by RSA.
For RADIUS-based token servers, such as ActivCard, CRYPTOCard, PassGo,
SafeWord, and Vasco, the standard RADIUS interface serves as the third-party
API.
Authenticating with External User Databases
Authenticating users with an external user database requires more than
configuring Cisco Secure ACS to communicate with an external user database.
Performing one of the configuration procedures for an external database that are
provided in this chapter does not on its own instruct Cisco Secure ACS to
authenticate any users with that database.