Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring the Optional Editing Rules Used by the SIC Group (SRC CLI)

    When you use explicit routing for the SIC, you can optionally specify an editing rule you want applied to the accounting or authentication request before SIC sends the request to the target. To configure editing rules, you define a source, conditions, and a target.

    Table 1 lists the available sources, conditions, and targets you can define in editing rules, and Configuration Statements for SIC Editing Rules (SRC CLI) provides a complete list of configuration statements used to define editing rules.

    Table 1: SIC Editing Rule Options

    Source

    Conditions

    Target

    SIC literal

    Match conditions:

    • Realm
    • User identity
    • Request attribute

    Condition tests:

    • Present
    • Not present
    • Equals
    • Does not equal
    • Has suffix
    • Has prefix
    • Within range

    Transactional variable

    Transactional variable

    RADIUS attribute in the request

    RADIUS attribute in the request

    RADIUS attribute in the response

    To configure an editing rule:

    1. From configuration mode, access the statement that configures the editing rule, and specify a name for the editing rule. For example, to create an editing rule called er1:
      [edit]user@host# edit shared sic group identifier editing er1
    2. Specify the editing mode.
      [edit shared sic group identifier editing er1]user@host# set mode (replace | append)

      Where:

      • replace—Current target (LValue) is replaced with the new value from the editing process
      • append—Current target (LValue) value is concatenated with the new target value from the editing process
    3. Define the source of the editing rule. The source can be a literal, transactional variable, or an attribute in the request. For example, to define a literal called literal1 as the source:
      [edit] edit shared sic group identifier editing er1 source literaluser@host# set literal1
    4. (Optional) If the source is a request attribute, you can also specify whether to remove the prefix, remove the suffix, remove before @, or remove after @.
      [edit ]user@host# edit shared sic group identifier editing er1 source request-attribute identifieruser@host# set remove-prefix remove-prefix
    5. Define the editing rule conditions, which include specifying the match conditions and the condition tests. See Table 1 and Configuration Statements for SIC Editing Rules (SRC CLI) for a complete list of configuration statements used to specify SIC editing rules. For example, to specify a condition that examines literals in accounting requests for the realm=abc.com:
      [edit]edit shared sic group identifier editing er1 literal literal1 condition realm equalsuser@host# set abc.com
    6. Define the target (where you want the result of the editing process to be placed) of the editing rule. The target can be a transactional variable, a RADIUS attribute in the request, or a RADIUS attribute in the response. For example, to place the results of the editing process in a variable called sic-variable1:
      [edit] user@host# edit shared sic group identifier editing er1 targetuser@host# set variable sic-variable1
    7. (Optional) Specify a default editing rule. You can set default editing rules for all three source types (literal, variable, and request attribute).
      [edit]user@host# edit shared sic group identifier editing editing-rule defaultuser@host# set literal literal

    Modified: 2016-12-29