Table of Contents
Advertisement
Chapter 11
Working with User Databases
Step 8
Token Servers with Vendor-Proprietary Interfaces
About Token Servers with Proprietary Interfaces
Configuring a SafeWord Token Server External User Database
78-13751-01, Version 3.0
Click Submit.
Result: Cisco Secure ACS saves the RADIUS token server database
configuration you created. You can add it to your Unknown User Policy or assign
specific user accounts to use this database for authentication. For more
information about the Unknown User Policy, see the
section on page
12-1. For more information about configuring user accounts to
authenticate using this database, see
Accounts."
Cisco Secure ACS supports several token servers by communicating via the token
server vendor's proprietary API.
For token servers supported by using the token server vendor's proprietary API,
Cisco Secure ACS acts as a token-card client to the token server. In some cases,
this means that the token-card client software is installed on the
Cisco Secure ACS server. In others, you must provide Cisco Secure ACS with
information about the token server. The token servers supported through their
vendor's proprietary API are as follows:
RSA SecurID—Cisco Secure ACS supports PPP (ISDN and async) and
•
Telnet for RSA SecurID.
SafeWord—Cisco Secure ACS supports PPP (ISDN and async) and Telnet
•
for SafeWord.
AXENT—Cisco Secure ACS supports PPP (over async only) and Telnet for
•
AXENT, not PPP with ISDN.
Cisco Secure ACS supports the SafeWord token server custom interface for
authentication of users. You can create only one SafeWord configuration within
Cisco Secure ACS.
Cisco Secure ACS 3.0 for Windows 2000/NT Servers User Guide
Token Server User Databases
"Unknown User Processing"
Chapter 7, "Setting Up and Managing User
11-53
Advertisement
Table of Contents
Troubleshooting
