Radiator Server Documentation — v10.34.0
Table of Contents
  • strict_reply_message

strict_reply_message

Use strict_reply_message in a RADIUS server block to select how Radiator handles Reply-Message in responses that also contain EAP-Message.

servers {
    radius "RADIUS_UDP_1812" {
        listen {
            protocol udp;
            port 1812;
            ip 0.0.0.0;
        }
        clients "CLIENTS_RADIUS_ALL";
        strict_reply_message true;
    }
}

The value is a boolean. The default is false.

When set to false, Radiator preserves Reply-Message in Access-Accept, Access-Reject, and Access-Challenge responses that contain EAP-Message. This compatibility mode supports deployments that use Reply-Message for reject reasons, reporting, or other NAS processing.

When set to true, Radiator removes Reply-Message from any response that contains EAP-Message. This mode follows the requirement in RFC 3579, section 2.6.5.

The setting does not convert Reply-Message to an EAP Notification. It only controls whether Radiator preserves or removes the RADIUS attribute.

Table of Contents
Navigation
  • @init

  • @verification

  • aaa

  • backends

  • caches

  • captures

  • certificates

  • clients

  • conditions

  • dictionary

  • handshake-timeout

  • hmac-otp

  • include

  • interval

  • ip-accept

  • license

  • logging

  • management

  • negotiation

  • proxy-protocol

  • scripts

  • servers

    • buffer

    • clients

    • http

    • ip

    • keepalive

    • policy

    • port

    • pre-client

    • protocol

    • radius

      • duplicate_cache

      • duplicate_detection

      • listen

      • status_server

      • strict_reply_message

    • tacacs-plus

    • timeout

    • tls

  • statistics

  • stats

  • timer

  • ui