About RADIUS Authentication and Accounting

The CMP system supports RADIUS Authentication and Accounting. You can configure the CMP system to operate in a network environment including multiple authentication servers, one authentication server, or no servers.

If both primary and secondary authentication servers are defined, the authentication process is as follows:
  1. The CMP system contacts the primary RADIUS server.

    If it responds with Accept or Reject, that action is followed.

  2. If the primary server does not respond within a specified number of retries or before a timeout value, the CMP system contacts the secondary RADIUS server (if defined).

    If it responds with Accept or Reject, that action is followed.

  3. If the secondary server does not respond, the CMP system authenticates against its local database (if enabled).
  4. If local authentication is not enabled, authentication fails.
  5. Theadmin user is always authenticated locally, regardless of configuration settings.

This process provides a fail-safe mechanism for accessing the CMP system even in the face of misconfiguration or network problems that cause the RADIUS servers to become inaccessible.

RADIUS configuration involves the following steps:
  1. See About Configuring the RADIUS Server for details on configuring the RADIUS server to accept authentication (and accounting, if used).
  2. See About Defining CMP Users to the RADIUS Server for details on defining CMP users in the RADIUS server.
  3. See About Associating Roles and Scopes for details on associating CMP users' roles and scopes with users on the CMP system
  4. See About Defining the CMP System as a RADIUS Client for details on configuring the CMP system to work with the RADIUS server.