Response attributes
Response attributes reference and configuration for Radius.
Response attributes can be configured for the following message types:
- Access-Accept
- Access-Challenge
- Access-Reject
Which attribute to set is specified using type code or name. The value supports property expansion (see below) and supports vendor specific attributes using the special syntax:
"value": "<vendor-id>:<sub-type>:<value>"//Example from attributes configuration{ "type": 26, "value": "12356:1:${item.spec_val}"}Attribute operation controls how the configured attribute should be "added" to the specified response:
CREATE: Attribute is created if and only if an attribute of same type does not already exist in the response (default).ADD: Attribute is added and the result may contain multiple attributes of the same type.REPLACE: Existing attributes (zero, one or many) of same type is replaced.COPY: All attribute of configured type is copied from request.
| Name | Description |
|---|---|
type | Attribute type. Mandatory unless name is specified. |
name | Attribute name. Mandatory unless type is specified. |
value | Attribute value. Supports property expansion. |
operation | Attribute operation (Default: "CREATE") |
{ "type": 18, "name": "Reply-Message", "value": "Have a nice day! (This message was generated at {{{now}}} [{{{request.name}}}#{{{request.id}}}])"}Property expansion context contains the following scopes:
- Request (
"request") - Session (
"session") - Pipe response Item (
"item")
| Name | Description |
|---|---|
id |
Numerical radius request packet identifier |
type |
Numerical radius request packet type (int) |
name |
Radius request packet type name |
| * | Named request attribute (both attribute type (ex "1") and name (ex "User-Name") are supported) |
| Name | Description |
|---|---|
id |
Session identifier |
trace_id |
Request trace id |
| * | Named session property |
| Name | Description |
|---|---|
id |
Item identifier |
| * | Named item property |