Owner's manual
Table Of Contents
- Chapter 1: Introduction
- Chapter 2: Accessing CC-SG
- Chapter 3: Configuring CC-SG with Guided Setup
- Chapter 4: Creating Associations
- Chapter 5: Adding Devices and Device Groups
- Chapter 6: Configuring Nodes and Interfaces
- Chapter 7: Adding and Managing Users and User Groups
- Chapter 8: Policies
- Chapter 9: Configuring Remote Authentication
- Chapter 10: Generating Reports
- Audit Trail Report
- Error Log Report
- Access Report
- Availability Report
- Active Users Report
- Locked Out Users Report
- User Data Report
- Users in Groups Report
- Group Data Report
- AD User Group Report
- Asset Management Report
- Node Asset Report
- Active Nodes Report
- Node Creation Report
- Query Port Report
- Active Ports Report
- Scheduled Reports
- CC-NOC Synchronization Report
- Chapter 11: System Maintenance
- Chapter 12: Advanced Administration
- Appendix A: Specifications (G1, V1, and E1)
- Appendix B: CC-SG and Network Configuration
- Appendix C: User Group Privileges
- Appendix D: SNMP Traps
- Appendix E: Troubleshooting
- Appendix F: Two-Factor Authentication
- Appendix G: FAQs
- Appendix H: Keyboard Shortcuts

CHAPTER 9: CONFIGURING REMOTE AUTHENTICATION 99
Chapter 9: Configuring Remote Authentication
Authentication and Authorization (AA)
Users of CC-SG can be locally authenticated and authorized on the CC-SG or remotely
authenticated using the following supported directory servers:
• Microsoft Active Directory (AD)
• Netscape’s Lightweight Directory Access Protocol (LDAP)
• TACACS+
• RADIUS
Any number of remote RADIUS, TACACS+, and LDAP servers can be used for external
authentication. For example, you could configure three AD servers, two iPlanet (LDAP) servers,
and three RADIUS servers.
Flow for Authentication
When remote authentication is enabled, authentication and authorization follow these steps:
1. The user logs into CC-SG with the appropriate user name and password.
2. CC-SG connects to the external server and sends the user name and password.
3. User name and password are either accepted or rejected and sent back. If authentication is
rejected, this results in a failed login attempt.
4. If authentication is successful, local authorization is performed. CC-SG checks if the user
name entered matches a group that has been created in CC-SG or imported from AD, and
grants privileges per the assigned policy.
When remote authentication is disabled, both authentication and authorization are performed
locally on CC-SG.
User Accounts
User Accounts must be added to the authentication server for remote authentication. Except when
using AD for both authentication and authorization, all remote authentication servers require that
users be created on CC-SG. The user’s username on both the authentication server and on CC-SG
must be the same, although the passwords may be different. The local CC-SG password is used
only when remote authentication is disabled. Please refer to
Chapter 7: Adding and Managing
Users and User Groups for additional information on adding users who will be remotely
authenticated.
Note: If remote authentication is used, users have to contact their Administrators to change their
passwords on the remote server. Passwords cannot be changed on CC-SG for remotely
authenticated users.