Cisco Cisco Access Registrar 5.0 데이터 시트
© 2005 Cisco Systems, Inc. All rights reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com.
Page 2 of 8
•
Whether authentication against a Lightweight Directory Access Protocol (LDAP) directory or Oracle database is required
•
Whether a request should be forwarded to an external RADIUS server
•
What type of accounting is required
•
Whether session limits apply
•
Whether an IP address pool has been assigned
While the basic operation of the server is determined by configuration, multiple extension points within the server provide optional callouts to
custom code. Extension points can be used for several purposes, including influencing the processing of a request or modifying incoming or
outgoing packets to meet specialized requirements.
Cisco Access Registrar provides a rich set of processing methods, including local, LDAP, Open Database Connectivity (ODBC), proxy, and prepaid,
but Cisco Access Registrar also permits custom service code to be inserted into its architecture to allow service providers to support special request
processing and system integration.
Figure 1. Cisco Access Registrar Architecture