This section will guide you through fields that apply to all identity provider (IdP) types. Review the Configuring Identity Providers page for information and prerequisites you’ll need before configuring IdPs.
To add or edit an IdP:
In the Identity Providers page (Identity > Identity Providers), click +Add and select the IdP type.
Complete the following fields:
Name. Enter a name for the IdP. This cannot be changed later.
Notes. Optional. Enter any notes about the IdP.
Tags. Optional. Add any tags to the IdP.
Complete the fields in the following sections:
Sign-in Settings
To configure the IdP’s sign-in settings, complete the following fields:
Prevent new device registrations that exceed this per user limit. All new devices are registered by the Controller. This prevents users registering more devices than the set limit. After registration is done, set the number to 0 to block new devices. The registration of new devices, through valid credentials, prevents one of the most common forms of breach: when stolen credentials are used to sign in to a system from a new device.
A cookie is created at sign-in and saved by the Controller and the client. This allows the Controller to perform additional checks at sign-in using this information. In the first instance, the device count is checked and access will not be allowed if the set limit been exceeded. If this check passes, you can require that users perform MFA at sign-in; either to register a new device (once), or for new and already-registered devices (always).
A registered device can be removed in two ways:
Delete the cookie from the client. See Device registration for details of this.
Delete the matching record on the Controller. See Registered Devices for more information.
MFA at Sign-in. Provides an additional restriction in respect of device registration. MFA can optionally be used with new devices or with new and already-registered devices. There are three modes available:
Not required (automatically register all devices)
Once (MFA required to register all new devices). Required to register any new device, as long as the new device registration count has not been exceeded.
Always (MFA required at every sign-in). Required whether a device has been registered or not, as long as the new device registration count has not been exceeded.
The recommended selection is Once (MFA required to register all new devices). This means a user onboards their own devices and is required to provide additional authentication at that time. Thereafter, the device effectively counts as a second factor when authenticating, mitigating the requirement for users to use MFA at every sign-in. See Multifactor authentication for more details. For Once or Always, an MFA provider must have been pre-configured:
MFA Provider. Choose which MFA provider to use for MFA at Sign-in.
Message. Message displayed to the user for the Require MFA user interaction. Defaults to a localized message in the client. The client will replace "%RADIUS_MESSAGE%" with the message from radius server (if any).
The following HTML tags are supported: 'a', 'b', 'i', 'strike', 's', 'strong', 'small', 'del', 'sub', 'sup', 'br', 'code', 'ol', 'ul', 'li', 'dl', 'dt', 'dd'
Claim Suffix. Enter a claim name for the Require MFA user interaction that will be passed to Gateways in the claims token. If you are configuring MFA at sign-in and also plan to use an MFA user interaction, use the same user response claim suffix for both. This ensures the user will not have to perform MFA twice over a short period of time.
Admin Access. Select Use for Admin UI sign-in to include this identity provider in the list of IdPs presented to the administrator.
Client settings
To configure the client settings for the IdP, complete the following fields:
Client Inactivity. When Enable timeout is selected, desktop clients will be signed out automatically when inactive.
Inactivity Timeout in Minutes. Set the inactivity timeout period after which the user will be signed out.
Timeout Trigger. Select between User inactivity only or User or network inactivity. The latter triggers when either are inactive. This feature is designed mainly to drop the open tunnels to the Gateways and prevent any background traffic being sent from unattended machines. It is not designed as a user security feature since the client often is configured to sign-in automatically. The user will see "Your session has timed out after being idle for too long."
Enforce Appgate connection as Domain network profile. Attempts to set the client's network adapter to run with a domain network profile. This is then used to influence local firewall settings. The network profile appears to use the following registry value but this is unsupported and undocumented by Microsoft. Its use is therefore not guaranteed and outcomes may depend on the version and build number of the underlying client operating system.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles\{<Network GUID>}
IP pools
To configure IP pool settings for the IdP, complete the following fields:
IPv4 Pool. Select a pre-configured pool of IP addresses to assign to clients authenticated through this IdP.
IPv6 Pool. Select a pre-configured pool of IP addresses to assign to clients authenticated through this IdP.
Claims
To configure claims settings for the IdP, complete the following fields:
Attributes Mapped to User Claims. Maps user attributes in the IdP directory to user claim names. This defines additional user claims for defining access criteria. For the local provider and Connector provider, a default list of mapped attributes is included. For LDAP providers, an example list of AD-mapped attributes is included. You can add your own attributes, and edit or delete included attributes.
Before you configure user access, change or add any user claims you want to use.
The User claim scripts section explains how to map extra claims. There is also a list of default user claims included in the AppGate ZTNA system.
Scripts Mapped to Device Claims. Scripts that run on a user’s device and return values mapped to device claims. The Device claims section explains how to use these scripts. There is also a list of all device claims included in the AppGate ZTNA system.
User Claim Scripts. Scripts used to make REST calls to external systems and return values mapped to user claims. The User claim scripts section explains how to use these scripts. There is also a list of all user claims included in the AppGate ZTNA system.