06.05.2013 Views

User Guide for Cisco Secure Access Control Server - Stewing Home

User Guide for Cisco Secure Access Control Server - Stewing Home

User Guide for Cisco Secure Access Control Server - Stewing Home

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Token <strong>Server</strong> <strong>User</strong> Databases<br />

12-50<br />

<strong>User</strong> <strong>Guide</strong> <strong>for</strong> <strong>Cisco</strong> <strong>Secure</strong> <strong>Access</strong> <strong>Control</strong> <strong>Server</strong> 4.2<br />

Chapter 12 <strong>User</strong> Databases<br />

Note If the primary and the secondary servers fail, ACS alternates between the servers until one<br />

responds.<br />

Step 8 Click Submit.<br />

ACS saves the proxy RADIUS token server database configuration that you created. You can add it to<br />

your Unknown <strong>User</strong> Policy or assign specific user accounts to use this database <strong>for</strong> authentication. For<br />

more in<strong>for</strong>mation about the Unknown <strong>User</strong> Policy, see About Unknown <strong>User</strong> Authentication, page 15-3.<br />

For more in<strong>for</strong>mation about configuring user accounts to authenticate by using this database, see<br />

Chapter 6, “<strong>User</strong> Management.”<br />

Token <strong>Server</strong> <strong>User</strong> Databases<br />

ACS supports the use of token servers <strong>for</strong> the increased security that one-time passwords (OTPs)<br />

provide.<br />

This section contains:<br />

About Token <strong>Server</strong>s and ACS, page 12-50<br />

RADIUS-Enabled Token <strong>Server</strong>s, page 12-51<br />

Using RSA Token-Card Client Software, page 12-54<br />

About Token <strong>Server</strong>s and ACS<br />

For in<strong>for</strong>mation about the types of authentication that ACS supports with token servers, see<br />

Authentication Protocol-Database Compatibility, page 1-8.<br />

Requests from the AAA client are first sent to ACS. If ACS has been configured to authenticate against<br />

a token server and finds the username, it <strong>for</strong>wards the authentication request to the token server. If it does<br />

not find the username, ACS checks the database that is configured to authenticate unknown users. If the<br />

request <strong>for</strong> authentication is passed, the appropriate authorizations are <strong>for</strong>warded to the AAA client<br />

along with the approved authentication. ACS then maintains the accounting in<strong>for</strong>mation.<br />

ACS <strong>for</strong> Windows Only<br />

ACS acts as a client to the token server. For all token servers except RSA SecurID, ACS acts as a client<br />

by using the RADIUS interface of the token server. For more in<strong>for</strong>mation about ACS support of token<br />

servers with a RADIUS interface, see RADIUS-Enabled Token <strong>Server</strong>s, page 12-51.<br />

For RSA SecurID, ACS uses an RSA proprietary API. For more in<strong>for</strong>mation about ACS support of RSA<br />

SecurID token servers, see Using RSA Token-Card Client Software, page 12-54.<br />

Solution Engine Only<br />

ACS acts as a client to the token server. For all token servers, ACS acts as a client by using the RADIUS<br />

interface of the token server. For more in<strong>for</strong>mation about ACS support of token servers with a RADIUS<br />

interface, see RADIUS-Enabled Token <strong>Server</strong>s, page 12-51.<br />

OL-14386-02

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!