15
15
%{proxy-reply:Attribute-Name} The value of the given Attribute-Name
16
16
in the proxy reply packet (if it exists)
18
The above variable expansions also support the meta-Attribute
18
The above variable expansions also support the meta-attribute
19
19
Packet-Type as well. See the RADIUS dictionary for details on its
22
22
%{check:Attribute-Name} Corresponding value for Attribute-Name
23
23
in check items for request
93
92
When attribute Bar is unset: returns literal string 'baz'
95
Multiple-valued attributes
96
--------------------------
98
%{Attribute-Name[index]}
99
Reference the N'th occurance of the given attribute. The
100
indexes start at zero. This feature is NOT available for
101
non-attribute dynamic translations, like %{sql:...}.
103
e.g. %{User-Name[0]} is the same as %{User-Name}
104
e.g. %{Cisco-AVPair[2]} references the value of the *third*
105
Cisco-AVPair attribute (if it exists) in the request
96
109
Attributes as environment variables in executed programs
97
110
--------------------------------------------------------
99
When calling an external program (e.g. from Exec-Program-Wait), these
100
variables can be passed on the command line to the program. In
101
addition, the server places all of the attributes in the RADIUS
102
request into environment variables for the external program. The
112
When calling an external program (e.g. from 'rlm_exec' module),
113
these variables can be passed on the command line to the program.
114
In addition, the server places all of the attributes in the RADIUS
115
request into environment variables for the external program. The
103
116
variables are renamed under the following rules:
105
118
1. All letters are made upper-case.
added
removed
doc/variables.txt
