RADIUS provider

Prev Next

This section describes how AppGate ZTNA works with RADIUS identity providers (IdPs).

AppGate ZTNA supports standard enterprise IdPs such as Active Directory (Entra ID). These IdPs authenticate users who connect through the client and administrators who sign in to the Controller Management interface.

Only the most basic functional integration is offered when interfacing to a RADIUS server. Ensure that AppGate ZTNA can meet your specific requirements before selecting this option.


Operation of RADIUS providers

With this IdP type:

  • The client passes the user's credentials to the Controller.

  • The service account (bind account) locates the user in AD. The service account is required because the username alone is not sufficient to bind.

  • This provides the Controller with the userPrincipalName for the user.

  • Using that information, the Controller binds using the username and password.

  • If the bind is successful, the user is authenticated successfully.

  • The Controller then queries AD for attributes and group memberships.


Prerequisites for a RADIUS provider

Configure your RAADIUS server for encrypted communication. If SSL is enabled and the RADIUS server has a valid certificate, the Controller automatically establishes an encrypted session with the directory server.


Shortening lookup times with a RADIUS provider

If an AppGate system relies on Active Directory (AD) group memberships, perform an audit of both user and machine group memberships before deployment. This audit helps clean up the directory structure and optimizes lookup performance.

Why lookup times matter

Lookup times directly affect authentication behavior:

  • The Controller waits up to five seconds for a response from the LDAP server.

  • If multiple LDAP servers are configured, the Controller moves to the next server after five seconds.

  • If only one LDAP server is configured, the Controller waits up to ten seconds.

  • Headless clients retry sign-in continuously until authentication succeeds.

In environments with many headless clients, repeated retries can flood Controllers with sign-in requests, which compounds any latency or availability issues in the directory servers.

Reducing lookup times through IdP configuration

To keep lookup times as short as possible, fully configure the identity provider. Specifically, use the Base DN, Membership Base DN, and Membership Filter fields to limit the scope of LDAP searches.

If these fields are not configured, LDAP searches span the entire directory tree, significantly increasing lookup time.

  • Base DN. Defines the portion of the LDAP tree that contains users. It may also include user groups, but the smaller the Base DN, the better the lookup performance.

  • Membership Base DN. Defines the portion of the LDAP tree that includes user groups. After a user is authenticated, the Controller performs a second LDAP query using this value to identify group memberships. If nothing is defined in this field, the Controller uses the Base DN.

  • Membership Filter. Further restricts the group search. Any filter configured here is concatenated with the search base and applied during the Controller’s group lookup query. Using a Membership Filter limits the number of objects evaluated, which helps reduce lookup times even further.

Group resolution behavior

How group membership is resolved depends on how Base DN is defined:

  • If Base DN includes only users, group membership is derived solely from the user record. For example:

    • The user record might list only sweden-sales

    • Nested group relationships, such as sweden-sales > sales > commercial, are not discovered.

  • If Base DN includes both users and groups, group membership is derived from group records.

    • The user is correctly identified as a member of sweden-sales, sales, and commercial.

Using Membership Base DN for performance and accuracy

Using Membership Base DN allows the Base DN to be minimized, which reduces the scope of the initial user search and shortens lookup times. Group searches are then performed against Membership Base DN, ensuring that all relevant group memberships— including nested groups—are returned.

This approach also reduces the scope of the second group lookup, further improving performance.

Using mulitple IdPs to shorten lookup times

The use of multiple IdPs can also minimize lookup times. If you have two different classes of users, such as human users with full clients and headless clients, you can create two different IdPs and use different Base DN, Membership Filter, and/or Membership Base DN values against an optimized tree structure. If your users were everywhere but the headless client users were recently added, then a filter like objectCategory=appgate-headless.* could be used.

The following is an example of an LDAP configuration:

Configuration settings for user filters and membership base for an LDAP identity provider.


Client authentication with a RADIUS provider

  • Client sign-in. When a RADIUS IdP has been selected on the client sign-in screen, enter the username and password. If Keep me signed in is selected, the client remembers the credentials and uses them to auto-start the next time the user signs in. The Controller maps attributes based on the entered username to populate user claims, and issues claims and entitlement tokens.

  • Claims token renewal. When the user's claims token expires, the client uses the cached username and password to renew the token automatically. If the credentials no longer match, the user is prompted to reauthenticate to renew the token.

  • Password user interaction. If a password user interaction is triggered, the client prompts the user to enter a password. This password might be for the IdP used to sign in, or it might be for a different IdP.

Administrator authentication with a RADIUS provider

These methods can also authenticate an administrator who signs in to the Controller admin UI and for REST API calls.


RADIUS User Interactions

RADIUS providers support different types of user interaction. AppGate ZTNA supports many of these through the standard RADIUS protocol. This section describes the three supported modes and how to use them. You can configure these three modes in different ways to support many RADIUS implementations.

Authentication modes

Flowchart illustrating AppGate and RADIUS server authentication processes with various access requests.

Mode

Description

AppGate ZTNA Preemptive OTP

Use this mode when the user has a token or app that generates a one-time password (OTP) before any RADIUS interaction starts. Typically, the user enters all credentials at once and then starts authentication.

There is no constraint on what the user can enter in the client when prompted for additional authentication. For example, the user can enter a term that the RADIUS server recognizes, which can then trigger a user interaction such as completing an additional step in a phone app.

RADIUS Server OTP

Use this mode for what many RADIUS providers call Push OTP. Typically, the RADIUS provider includes a phone app that the RADIUS server communicates with. The app can perform additional authentication steps such as approving a prompt, entering an OTP, or performing a fingerprint scan. When the RADIUS server accepts the response, it sends an Access-Accept message.

AppGate ZTNA Client Interaction using RADIUS Challenge-Request Method

This mode is the traditional, challenge-based RADIUS use case. Here, the AppGate ZTNA client provides the user interaction on behalf of the RADIUS server. Currently, the only supported interaction type is OTP, where the user typically enters a 4- or 6-digit code.

In this mode, the client displays a message from the AppGate ZTNA system, or it uses the Reply-Message (24) included in the Access-Challenge (4) message from the RADIUS server.

In all three modes, if a RADIUS Access-Reject (3) message is received, it may include a Reply-Message (18). If present, the message is passed to the client and written to the client log file.

Multiple RADIUS MFA Providers

You can configure more than one method of additional authentication. AppGate ZTNA supports this by using multiple MFA providers.

To use multiple RADIUS providers, configure the RADIUS server with two instances of the AppGate ZTNA system. Configure the second instance (often referred to as a RADIUS client) with an alternative authentication method and a different port (not 1812). Then configure AppGate ZTNA twice—once for each RADIUS client—and match the port numbers you configured earlier. This also works with two distinct RADIUS servers.

This configuration is not intended to provide high availability (HA). The two MFA providers appear to the administrator and user as two distinct MFA user interaction types.