CloudLabBox
Try the free demo

FortiGate lab 11 of 25

LDAP and RADIUS authentication

Connect FortiGate to the company directory over LDAP and to a RADIUS server, map directory groups to firewall groups, give Engineering and Finance different access, let IT admins log in with their directory accounts, and debug authentication from both ends.

Run this lab

It needs Lite: its 4 nodes are set to 4 vCPU and 6,144 MB in total. That fits the free demo too.

In your workspace: Shared, then FortiGate NSE 4 guided labs, then 11 - LDAP and RADIUS authentication

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 70 minutes
Nodes need
4 vCPU, 6,144 MB
Smallest plan
Lite

The scenario

Local accounts don't scale, and Harbourside now has a directory server, SRV1, which answers LDAP like Active Directory and also runs RADIUS for network devices. The rules: Engineering may browse the web, Finance may browse the web too (the finance VPN team also wants RADIUS ready, with a Finance group, for its own use), and members of IT-Admins must be able to log in to the FortiGate with their own directory accounts instead of the shared admin password.

DeviceInterfaceAddressConnects to
FGT1port2 (LAN)10.1.10.1/24PC1 10.1.10.10
FGT1port3 (SERVERS)10.1.30.1/24SRV1 10.1.30.10 (directory)
FGT1port1 (ISP-A)203.0.113.1/24INET, gateway 203.0.113.254

Directory facts (teaching values): base DN DC=corp,DC=lab; users in OU=People, groups in OU=Groups; login name attribute sAMAccountName; group membership in memberOf; bind account CN=fgt-bind,OU=Service,DC=corp,DC=lab / BindPass1!; RADIUS shared secret RadSecret1!; every user's password is Training1!.

What you’ll practise

  • Explain LDAP bind types (simple, anonymous, regular), the base DN and the common name identifier
  • Configure an LDAP server, test credentials and read group membership
  • Configure a RADIUS server and use Fortinet-Group-Name for group matching
  • Build firewall groups that match remote groups and use them in policies
  • Create remote administrators with a wildcard account
  • Debug authentication with diagnose test authserver and fnbamd

The tasks

  1. Start the lab
  2. Look at the directory
  3. An LDAP server with a regular bind
  4. A RADIUS server
  5. Map directory groups to firewall groups and use them
  6. Directory administrators
  7. Debug authentication

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of LDAP and RADIUS authentication4 nodes, 3 links. Every link is listed as text below the diagram.FGT1INETPC1SRV1port1eth0port2eth0port3eth0
4 nodes, with the interface names each link uses.
Every link, as text
  • FGT1 port1 to INET eth0
  • FGT1 port2 to PC1 eth0
  • FGT1 port3 to SRV1 eth0
Nodes in LDAP and RADIUS authentication, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
FGT1Fortinet FortiGatefortinet-FGT-v7.0.17.M-build06821 vCPU, 2,048 MB
INETEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
PC1EVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 2,048 MB
SRV1EVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder FortiGate NSE 4 guided labs.

  3. Open 11 - LDAP and RADIUS authentication and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More FortiGate labs

All FortiGate labs

Related labs in other courses

CloudLabBox is independent of Fortinet. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.