RADIUS Two-Factor Authentication for Operator Staff and Enterprise Services

TLDR

  • An Access-Challenge (RFC 2865 §4.4) carries the second factor in RADIUS, and the State attribute (§5.24) ties the follow-up request back to the first.
  • There are three ways to add MFA: append an OTP to the password, use challenge-response, or send an out-of-band push.
  • OTP patterns work with normal RADIUS timeouts. Push needs NAS timeouts of roughly 30 to 60 seconds.
  • A NAS that can’t handle challenges must treat Access-Challenge as Access-Reject.

RADIUS supports two-factor authentication through the Access-Challenge message: after checking the password, the AAA server returns a challenge with a State attribute, and the NAS sends a second Access-Request carrying the one-time code. Push-based MFA instead holds the request open until the user approves, so NAS timeouts must be raised to match.

RADIUS (Remote Authentication Dial In User Service) was built around one request and one answer. A second factor either stretches that exchange or adds a round trip. The network access server (NAS) relaying each login decides which of the two it can live with.

So RADIUS two-factor authentication starts with the NAS fleet, well before anyone picks an authenticator app. That’s the first job for AAA (authentication, authorization and accounting) engineers adding multi-factor authentication (MFA) for staff, enterprise customers and managed services. For the fundamentals, see what an AAA server does.

How RADIUS two-factor authentication works: Access-Challenge and State

In RADIUS two-factor authentication, an Access-Challenge carries the prompt and the State attribute links the two Access-Requests. Both are defined in Request for Comments (RFC) 2865 (§4.4, §5.24).

Without MFA, a login is one exchange. The NAS sends an Access-Request (§4.1) with User-Name (§5.1) and User-Password, hidden with the shared secret (§5.2). It gets back Access-Accept or Access-Reject (§4.2, §4.3).

MFA adds a step in the middle. Once the password checks out, the server sends an Access-Challenge instead, with prompt text in Reply-Message (§5.18) and one State attribute.

The NAS shows that prompt, then sends a fresh Access-Request with a new Identifier. The code rides in User-Password, next to the State value copied from the challenge.

What the State attribute does in RADIUS MFA

State is an opaque value the AAA server makes up. Under §5.24, the NAS must send it back unmodified and must not interpret it. That lets the server use it to find the pending login.

Treat it as single-use: reject any value that’s unknown, expired or already answered. If a device anywhere in the path drops or rewrites State, even a correct code fails.

Three RADIUS MFA integration patterns: OTP, challenge and push

RADIUS multi-factor authentication carries the second factor in the password field, in a reply to an Access-Challenge, or over a separate push channel.

Pattern 1: OTP appended to the password

The user types their password with a one-time password (OTP) tacked on the end. The AAA server splits the two and checks each. The code comes from an app or token running TOTP (Time-Based One-Time Password, RFC 6238) or HOTP (HMAC-Based One-Time Password, RFC 4226).

All it needs is PAP (Password Authentication Protocol), which RFC 2865 §2.2 maps straight onto User-Password. CHAP (Challenge-Handshake Authentication Protocol) sends a hashed response, so there’s nothing to split. Our guide to RADIUS methods compares both, along with the other options.

One RADIUS MFA best practice covers every code-based pattern: accept each code only once (RFC 6238 §5.2), and throttle failed attempts (RFC 4226 §7.3).

Pattern 2: Access-Challenge challenge-response

The server checks the password, then sends an Access-Challenge whose Reply-Message asks for the code. The user types it at a second prompt, and the NAS returns it with State.

It’s the clearest of the three for users, and the prompt can be worded per user group. The catch is that the NAS must support challenge-response for that login type.

Pattern 3: Out-of-band push

After the password check, the AAA server, or an on-premise MFA server it calls, sends a push to the user’s phone. It holds the Access-Request open until the user approves or the approval window closes.

No code travels inside RADIUS, so push works with PAP and CHAP alike. The cost is time, because the NAS has to keep waiting.

Teams following the National Institute of Standards and Technology (NIST) guidelines in Special Publication (SP) 800-63B-4 have one more rule. Sections 3.1.3 and 3.1.3.1 no longer accept approve-only prompts, which attackers abuse by flooding users until someone taps yes. Over RADIUS, pair push with an Access-Challenge whose Reply-Message shows a number to enter in the app.

Getting RADIUS MFA timeout settings right

A RADIUS timeout is how long a NAS waits for a reply before it retransmits. Push MFA only works when that wait outlasts the user’s approval.

When the per-attempt timeout has run out on every attempt, the NAS fails over to the next server (RFC 2865 §2). Retransmissions keep the same Identifier, which lets the server spot duplicates (§2.5, §3). A server that misses them, or a backup server after failover, sends a second push.

Picture a regional internet service provider (ISP) adding push MFA for network operations center (NOC) engineers on a virtual private network (VPN) gateway. The gateway waits 5 seconds per attempt with two retries, so it fails over at 15 seconds. An engineer who approves at 18 seconds gets a failed login, then a second push.

The fix is a 45-second gateway timeout with one retry and a 30-second approval window on the AAA side, so the server answers first. In deployments we see this failure reported as duplicate push prompts more often than as timeouts.

The server’s own processing barely registers here. The Alepo AAA Server datasheet lists sub-millisecond latency, so the wait belongs to the user and the push channel.

Table 1. RADIUS MFA timeout guidance by pattern (starting ranges)

Pattern NAS timeout per attempt NAS retries AAA-side setting
OTP appended 3–5 s 2–3 Normal processing; no extra wait
Challenge-response 3–5 s 2–3 Keep State valid for 60–180 s while the user types
Out-of-band push 30–60 s 0–1 Approval window 5–15 s shorter than the NAS timeout

Challenge-response is different: the user types between packets, so the RADIUS timeout can stay short. What has to match is the NAS prompt and the State lifetime. A Session-Timeout (§5.27) in the challenge can cap the prompt, where the NAS honors it.

TOTP adds its own clock. RFC 6238 §5.2 recommends a 30-second time step and at most one step of allowance for network delay.

How to add RADIUS MFA without breaking legacy NAS equipment

Under RFC 2865 §4.4, a NAS without challenge support must treat Access-Challenge as Access-Reject. A challenge sent to legacy equipment simply fails the login.

Let the AAA server pick the pattern per NAS group, telling groups apart by NAS-IP-Address or NAS-Identifier (§5.4, §5.32). Keeping that logic on a carrier-grade AAA server limits NAS changes to timeouts.

  1. List each NAS model’s authentication method, and note whether its RADIUS timeout can be adjusted.
  2. In a lab, send each model an Access-Challenge and record whether it prompts or rejects.
  3. Map each group to a pattern in AAA policy.
  4. Roll out group by group, keeping a vaulted local emergency account on each device.

Table 2. Which RADIUS MFA pattern each kind of NAS tolerates

Pattern NAS must support Password sent as PAP NAS timeout change Best legacy fit
OTP appended PAP Yes None PAP-only equipment
Challenge-response Access-Challenge prompts Yes, for the code None NAS models that pass the lab test
Out-of-band push An adjustable RADIUS timeout No (CHAP works) Raise to 30–60 s CHAP-only NAS with an adjustable timeout

Some sessions never show a prompt, such as subscriber broadband logins from a home router. Leave those outside MFA policy.

RADIUS MFA for operator staff vs. enterprise customers

RADIUS MFA for staff protects the operator’s own network. Customer MFA is part of a service the operator runs, so each needs its own policy.

Operator staff and device admin logins

Staff logins include VPN access to management networks, operations and business support system (OSS/BSS) portals, and command-line access to broadband network gateways (BNGs) and routers. RADIUS MFA for network devices works wherever the management login supports your chosen pattern.

Device administration often runs on TACACS+ (Terminal Access Controller Access-Control System Plus), which adds per-command authorization. Alepo’s TACACS+ Server covers that side, and our TACACS+ MFA checklist covers second factors for privileged roles.

NIST SP 800-63B-4 §3.2.5 doesn’t count OTP or out-of-band methods as phishing-resistant. So staff MFA works best as one layer in a wider zero trust and AAA design.

Enterprise and managed-service customers

For managed VPN or Wi-Fi, the operator’s AAA server can proxy requests to the customer’s own RADIUS server and MFA (RFC 2865 §2.3). The proxy passes Access-Challenge and State through unchanged. Per-customer policy then sets the pattern and the prompt wording.

Timeouts stack across that chain, so each upstream hop must wait longer than the hop behind it. For RADIUS MFA on enterprise Wi-Fi, check the controller’s 802.1X timers before switching on push.

FAQs

Q1. Does RADIUS support two-factor authentication?

Yes: the Access-Challenge message (RFC 2865 §4.4) lets the AAA server ask for a one-time code after the password checks out. The State attribute links the two requests. RADIUS can also carry a code appended to the password, or wait while the user approves a push.

Q2. How does the RADIUS Access-Challenge flow work?

The server answers the first Access-Request with a Reply-Message prompt and a State value. The NAS collects the code and sends a new Access-Request containing the code and the unchanged State. The server checks both, then returns Access-Accept or Access-Reject.

Q3. Should I use push or OTP for RADIUS MFA?

OTP runs on more NAS equipment because the timeouts can stay as they are. Push is easier on users and works with CHAP, but it needs NAS timeouts of about 30 to 60 seconds. Under NIST SP 800-63B-4, push also needs a number that the user enters in the app.

Q4. Why do RADIUS MFA logins time out?

Usually the NAS stops waiting before the user approves a push, then retransmits or fails over, which can set off a second push. Set the NAS timeout above the AAA server’s approval window so the server always answers first.

Q5. Will MFA work with older NAS equipment?

Usually, as long as the pattern fits the device. Older NAS models that reject challenges can use OTP appended to the password, or push where the timeout can be raised. Test each model in a lab before rollout.

Q6. Can MFA protect device admin logins?

Yes, as long as the management login uses RADIUS and supports the chosen pattern. Device administration often runs on TACACS+ instead, which adds per-command authorization and can require a second factor for privileged roles.

Q7. Where should MFA be enforced, on the NAS or the AAA server?

On the AAA server. Central enforcement gives you one policy, one audit trail and a pattern for each NAS group. Enforcing MFA device by device multiplies configuration and leaves gaps wherever support is missing.

Q8. Can RADIUS 2FA protect VPN access?

Yes. Two-factor authentication (2FA) over RADIUS works on a VPN gateway because the gateway is a RADIUS client like any other NAS. Check whether it shows Access-Challenge prompts to users, and whether its RADIUS timeout can cover push approval.

Conclusion

RADIUS can carry a second factor with tools RFC 2865 already defines. Access-Challenge and State handle the code exchange. Appended OTPs cover PAP-only equipment, and push covers CHAP-only gear that can wait.

Most of the effort goes into three choices. Pick a pattern per NAS group, set timeouts so the AAA server answers first, and keep MFA policy in one place.

Get those right, and staff, enterprise customers and managed services gain a second factor. NAS equipment that fits one of the three patterns stays in service.

Book a demo to see the Alepo AAA Server and talk to an expert about MFA integration for staff access and managed enterprise services.

Want to see how this applies to your business? Let’s talk.

Share the Post:

Latest Posts

Receive the latest news

Subscribe To Our Newsletter

Subscribe to our Newsletter

Receive the latest news

Subscribe To Our Newsletter