Multifactor authentication in AppGate ZTNA

Prev Next

AppGate ZTNA uses multifactor authentication (MFA) to provide additional protection during authentication. MFA can be applied in the following areas:


MFA at sign-in

NOTE

To configure MFA at sign-in, see the Sign-in Settings in the General IdP Settings section.

MFA at sign-in controls device registration. Device registration prevents unauthorized access when valid credentials are used from a new device.

AppGate ZTNA creates a cookie at sign-in that is stored by both the Controller and the AppGate client. This cookie is presented during future connection attempts. The Controller then checks the device registration limit. If the device registration limit has not been exceeded, MFA can be enforced based on the configured MFA mode.

MFA modes

There are three modes available:

  • Not required (automatically register all devices).

  • Once (MFA required to register all new devices). Requires MFA to register each new device, provided the device registration limit has not been exceeded.

  • Always (MFA required at every sign-in). Requires MFA at every login, provided the device registration limit has not been exceeded.

IMPORTANT

The Always mode can interfere with background operations such as automatic sign-in, token renewal, and browser launches when SAML tokens expire. Consider overall system behavior before enabling this option.

Portal behavior with MFA

Device registration has the following differences with the Portal:

  • The cookie is saved only if Remember me is selected at sign-in.

  • The cookie is deleted when the user signs out, which assumes the device is shared or public.

After configuring and provisioning an MFA provider, best practice is to use the Once (MFA required for new devices) mode.

If MFA is configured both at sign-in and as a user interaction, using the same user response claim suffix for both prevents users from being prompted for MFA twice in a short period.


MFA user interaction (user access)

Instead of enforcing MFA at sign-in, AppGate ZTNA applies MFA dynamically when users request access to specific resources. This approach allows administrators to apply stronger authentication only where it is required.

For example:

  • Standard services such as email can be available to all authenticated users.

  • Sensitive resources can require additional authorization at the Gateway, such as MFA or password reauthentication.

MFA user interactions are configured within Conditions. For more information, see User interactions.


MFA for admins (administrator access)

MFA can be required for administrators accessing the admin UI. Exceptions can be configured to allow API-based access.

MFA for administrators is strongly recommended, including access from internal networks. For guidance on securing access to port 8443, see System security – best practices. For configuration details, see Admin user access.

See the MFA for Admins section for more information.


Supported MFA providers

AppGate ZTNA supports both built‑in MFA providers and external RADIUS providers.

Built-in providers

The following built-in providers include:

  • Time-based one-time password (OTP). The built-in Time-Based OTP provider works with most OATH-compliant authenticator applications. Users initialize the authenticator using a QR code the first time MFA is triggered.

  • FIDO2. Works with FIDO2-compatible USB devices. Authentication requires inserting and touching the device when prompted. For more information, see Default FIDO2 provider.

External providers

RADIUS is supported as an external MFA provider. RADIUS supports preemptive, RADIUS-based, and challenge-response authentication modes. For more information, see RADIUS provider.

Using an IdP as an MFA provider

The Password user interaction can be used as an MFA mechanism by requiring reauthentication at a specific point in the access flow. For true MFA, use a different IdP than the one configured for sign-in.

Requirements

  • The username for the MFA IdP must match the username used by the sign-in IdP.

  • When using a SAML IdP, the Password user interaction can support alternative MFA methods, such as Azure MFA.

Configuration overview

User action prompt requesting password input and identity provider selection options.

To use a SAML IdP for MFA:

  1. Create a secondary SAML IdP linked to the same username as the primary sign‑in IdP.

  2. Configure the secondary IdP to use an MFA‑only method, such as push notifications.

  3. Add the secondary IdP to AppGate ZTNA and link it to the SAML configuration.

  4. Select this IdP when configuring the user interaction in a condition.

When the user interaction is triggered, the user completes MFA in a browser. The SAML authentication response is accepted by AppGate ZTNA as a valid password user interaction.