This guide provides an overview of all supported RADIUS Authentication, Authorization and Accounting attributes.
Topics include:
The authentication attributes are organized per application. The accounting attributes are organized per accounting application. For each application, three tables provide the attribute details:
Description — A detailed description per attribute
Limits — Value limits and format description per attribute. Note that the SR OS RADIUS Python interface enables flexible formatting of the attributes received from and sent to the RADIUS AAA servers.
Applicability — RADIUS messages where the attribute can be present
Table 1 lists and describes the attribute conventions used in this guide.
| Attribute | Description |
|---|---|
|
0 |
This attribute must not be present in packet. |
|
0+ |
Zero or more instances of this attribute may be present in packet. |
|
0-1 |
Zero or one instance of this attribute may be present in packet. |
|
1 |
Exactly one instance of this attribute must be present in packet. |
Attribute Type Identifiers and VSA Type Identifiers used in this guide follow the dotted number notation as described in RFC 6929, Remote Authentication Dial In User Service (RADIUS) Protocol Extensions. For example:
1 (User-Name), a standard attribute type
26.6527.11 (Alc-Subsc-ID-Str), A Nokia Vendor Specific Attribute: Attribute type 26, Vendor Id 6527 and VendorType 11.
241.26.6527.16 (Alc-IPv6-Router-Adv-Policy), A Nokia Extended-Vendor-Specific-1 Attribute: Attribute Type 241, Extended Type 26, Vendor Id 6527 and Vendor Type 16.
All Nokia Vendor Specific Attributes (VSAs) are available in a freeradius dictionary format. The dictionary is delivered together with the software package: <cflash>\support\dictionary-freeradius.txt.