Figure 1: Control Policy Structure Control Policy Configuration Overview Control policies express system functionality in terms of an event, a condition, and an action. There are three steps in defining a control policy: 1. Create one or more control classes—A control class specifies the conditions that must be met for a control policy to be activated. A control class can contain multiple conditions, each of which will evaluate as either true or false. Match directives specify whether all, any, or none of the individual conditions must evaluate true for the class to evaluate true. Or, you can specify the default control class which does not contain any conditions and always evaluates true.
2. Create a control policy—A control policy contains one or more control policy rules. A control policy rule consists of a control class, an event that causes the class to be evaluated, and one or more actions. Actions are numbered and executed sequentially. 3. Apply the control policy—A control policy is activated by applying it to an interface. Parameter Maps for Cisco Identity Based Networking Services A parameter map allows you to specify parameters that control the behavior of actions specified under a control policy. For Cisco IBNS, an authentication parameter map defines parameters used for the action specified with the authenticate using webauth command.
You can configure the following types of parameter maps: • Authentication bypass (This is also called nonresponsive host [NRH] authentication.) • Consent • Web authentication Configuring Identity Control Policies Control Policy Configuration Overview Configuring Identity Control Policies 3