Description | This article describes the basic configuration steps required to integrate the Jumpcloud LDAP server into FortiGate. |
Scope | FortiGate. |
Solution |
For the regular LDAP user to log in, the LDAP binding user has to be configured to gain access to the LDAP directory to facilitate authentication requests.
This user need not be a service account. Any JumpCloud user can be set as a binding user but should be treated as a privileged user.
Sample config in the GUI:
Sample config in the CLI:
The sample CLI configuration is as follows:
config user ldap next
cnid is set to uid instead of cn/sAMAccountName. UID is an LDAP account attribute that stores a username.
Note: The highlighted text (2 CLI commands) must be configured to match the group matching when using LDAP user/user groups for VPN. When verifying the user on LDAP using the ‘Test User Credentials’ button, it will work without these 2 commands. These 2 attributes can only be configured using CLI.
Group member checking methods can be assigned using the following CLI command:
Fortigate (Jumpcloud_LDAP) # set group-member-check Filter used for group searching can be assigned using the following CLI command:
Fortigate (Jumpcloud_LDAP) # set group-object-filter
The username would be in the format uid=<userid>,ou=xxxxx,o=xxxxxxxxxxxxxxxxxx,dc=jumpcloud,dc=com.
If MFA is in use, consider the following:
So far, there is not an easy solution to support MFA when connecting to WPA_Enterprise SSID. The push time will be 5 seconds. This timer cannot be changed. For a wired ethernet connection, it is possible to change the push timer with the remoteauthtimeout value:
config system global set remoteauthtimeout <----- Specify a value in seconds. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.