Radiator Server Documentation — v10.34.2
Table of Contents

conditions

Policy conditions select which requests a policy handles. Without conditions, a policy matches every request. A condition rule contains a namespace attribute, a comparison operator, and one or more values.

Configuration checks warn when multiple policies omit conditions, including policies in different files. These configurations remain valid; policies and handlers are evaluated in configuration order. Use policy conditions such as aaa.protocol == protocol.RADIUS to make selection explicit. Put the protocol check in the policy's conditions all block; use handler conditions to select request types within that protocol.

Policy conditions are defined as:

conditions <all | any | none> {
    <condition rules>
}

The condition block uses the all, any, or none matching strategy and can contain comparisons and nested condition blocks. For the matching strategies, nesting, evaluation order, and comparison operators, see Condition Blocks. Handler conditions use the same syntax.

For example, the following policy handles RADIUS requests in the corp realm and RADIUS requests from the admin user in any realm:

conditions all {
    aaa.protocol == protocol.RADIUS;
    any {
        aaa.identity.realm == "corp";
        aaa.identity == "admin";
    }
}