---
title: "System configuration"
slug: "system-configuration-v6-5"
description: "Prepare your AppGate appliances for user access by integrating Identity and MFA providers, ensuring a secure and efficient configuration process."
updated: 2025-12-04T15:21:01Z
published: 2025-12-04T15:21:01Z
canonical: "support.appgate.com/system-configuration-v6-5"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.appgate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# System configuration

This section outlines the steps you need to take to prepare Appgate SDP appliances prior to configuring user access. You might be familiar with many of the steps, such as integrating with primary authentication and multi-factor providers:

[**Identity Providers**:](/v1/docs/authentication-services) Designed for multi-tenant deployments. Because a different tenant would likely use a different Identity Provider (IdP), several of the configuration options are tied to the IdP. Currently, Appgate SDP supports connections to [LDAP/AD](/v1/docs/ldapradius-identity-providers), [LDAP Certificate](/v1/docs/ldap-certificate-identity-providers), [RADIUS](/v1/docs/ldapradius-identity-providers), [OIDC](/v1/docs/oidc-identity-providers), and [SAML](/v1/docs/saml-identity-providers) IdPs. The Controller also maintains a local database providing an additional directory for local user accounts. The first thing to do is set up your IdP. Once this is done, you can test this by setting up some new admin roles and users, and then see if you can log in to the admin UI using credentials from your chosen IdP.

[**MFA Providers**](/v1/docs/claim-harvesting-multi-factor-authentication): Enable one of the key aspects of Appgate SDP's security model: [Multi-stage authorization](/v1/docs/multi-stage-authorization). This is not reliant on additional authentication, such as OTP, but AppGate recommends that one or more MFA Providers are configured because the system can use them in three different ways: administrator access, registering devices at sign-in, and user interactions. Configure a RADIUS-based MFA Provider. If you do not have one, you can use the built-in default, time-based OTP provider which works with most authenticator apps. You can test this is by enabling this for your admin users since you have set these up already. Exclude the built-in admin to make sure you don't lock yourself out.

Other configurations might be less familiar, so it might be worth looking at [DNS and name resolution](/v1/docs/dns-and-name-resolution-2), [Portal](/v1/docs/portal), and [Connector](/v1/docs/connectors) to understand how to best integrate the Appgate SDP solution into your network environment.

![Flowchart illustrating user access configuration with ID and MFA providers.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/ag55-system_config.png?sv=2026-02-06&spr=https&st=2026-10-27T08%3A04%3A07Z&se=2026-10-27T09%3A04%3A07Z&sr=c&sp=r&sig=8aMCtlDQ6ztrsGycMXvx4m0Sa6xvJj5hZu%2BfWNVXGu4%3D)

Appgate SDP (Software Defined Perimeter) is a security solution that provides secure access to resources based on user identity and context, leveraging a zero trust security model.

The Controller is the central management appliance in the Appgate ZTNA system, responsible for user authentication, policy distribution, and overall system administration.

A component that extends connectivity to remote sites and unmanaged resources without requiring the use of a standalone Client.