dictionary

Configures protocol dictionaries. Currently used for RADIUS dictionaries.

A dictionary file defines human-readable names for protocol attributes and values. It maps numeric attribute identifiers to readable names and defines the data type for each attribute.

Only one dictionary{} definition is used. If you add multiple last one read will override. In order to add multiple files use the multiple filename directives.

Default Dictionary

When no dictionary configuration is present, the server automatically attempts to load the default RADIUS dictionary from /opt/radiator/server/dictionary. If this file exists, it is loaded. If it does not exist, the server continues to operate without a dictionary.

Explicitly configured dictionaries always take precedence over the default.

Example

dictionary {
    radius {
        filename "dictionary/dictionary";
    }
}

Reloading Dictionaries

Dictionaries can be reloaded without restarting the server. Changes to dictionary files or configuration take effect immediately after reload.

Via HTTP Management API

Reload the RADIUS dictionary using the management API with basic authentication:

curl -X POST http://localhost:8080/api/v1/dictionary/radius/reload \
  -u admin:password

This triggers a hot reload of all configured dictionary files.

Via Configuration Update

When deploying a new configuration that includes dictionary changes through the management UI or API, the dictionary is automatically reloaded as part of the configuration update process.

No service interruption or restart is required for dictionary changes.