CloudLabBox
Try the free demo

FortiGate lab 10 of 25

Local users and captive-portal authentication

Turn anonymous internet access into identity-based access: local users and groups, DNS allowed before login, a captive portal that appears for web traffic, different rights for staff and guests, and the commands to see and clear who is logged in.

Run this lab

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

In your workspace: Shared, then FortiGate NSE 4 guided labs, then 10 - Local users and captive-portal 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 55 minutes
Nodes need
4 vCPU, 5,632 MB
Smallest plan
Lite

The scenario

Harbourside's open office also hosts visitors, and the internet policy currently lets anyone on the LAN out. From today, people must sign in: staff (jsmith and mlopez) get the web, and the visitor account tguest gets only the company's own site, www.example.com. There is no directory server yet, so the accounts live on the FortiGate.

DeviceInterfaceAddressConnects to
FGT1port1 (ISP-A)203.0.113.1/24INET, gateway 203.0.113.254
FGT1port2 (LAN)10.1.10.1/24PC1 10.1.10.10 (Firefox), H1 by DHCP

Accounts to create (teaching password for all: Training1!): jsmith and mlopez in group Staff, tguest in group Guests.

What you’ll practise

  • Create local users and firewall user groups
  • Explain which protocols trigger active authentication and why DNS must be allowed first
  • Write identity-based policies that give staff and guests different access
  • Log in through the captive portal from a browser and from the command line
  • Monitor authenticated users, set timeouts and log users out

The tasks

  1. Start the lab
  2. Local users and groups
  3. Allow DNS before anyone logs in
  4. Identity-based policies for staff and guests
  5. Log in from the command line and test the guest
  6. See, time out and clear users

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 Local users and captive-portal authentication4 nodes and 1 network, 4 links. Every link is listed as text below the diagram.FGT1INETPC1H1LANport2eth0eth0port1eth0
4 nodes and 1 network, with the interface names each link uses.
Every link, as text
  • FGT1 port1 to INET eth0
  • FGT1 port2 to LAN (network)
  • PC1 eth0 to LAN (network)
  • H1 eth0 to LAN (network)
Nodes in Local users and captive-portal 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
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 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 10 - Local users and captive-portal 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.