FortiGate lab 12 of 25
Passive authentication: RSSO and FSSO
Identify users without a login prompt: let a network access server's RADIUS accounting tell FortiGate who is on which address (RSSO), build policies on those identities, then set up and troubleshoot the FSSO side of the same idea for Active Directory.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 6,656 MB in total. That fits the free demo too.
In your workspace: Shared, then FortiGate NSE 4 guided labs, then 12 - Passive authentication - RSSO and FSSO
- Level
- Advanced
- Time
- About 60 minutes
- Nodes need
- 5 vCPU, 6,656 MB
- Smallest plan
- Lite
The scenario
Engineers hate the login page from lab 10: their laptops already authenticate to the network through Harbourside's network access control (NAC) system, which sends RADIUS accounting messages saying "user bkhan is now on 10.1.10.50". The security lead wants FortiGate to reuse that identity, so engineers get the web with no prompt, while machines with no identity (such as PC1) get nothing. Head office also runs Active Directory, so you'll prepare the FortiGate side of Fortinet single sign-on (FSSO) for when the collector is installed.
| Device | Interface | Address | Role |
|---|---|---|---|
| FGT1 | port2 (LAN) | 10.1.10.1/24 | H1 10.1.10.50 (bkhan's laptop, reserved), PC1 10.1.10.10 |
| FGT1 | port3 (SERVERS) | 10.1.30.1/24 | SRV1 10.1.30.10 plays the NAC and the future FSSO collector |
| FGT1 | port1 (ISP-A) | 203.0.113.1/24 | INET, gateway 203.0.113.254 |
Teaching values: RADIUS accounting secret RadSecret1!; the NAC puts the user's group in the RADIUS Class attribute (bkhan → Engineering).
What you’ll practise
- Compare active and passive authentication and when each fits
- Configure RADIUS single sign-on (RSSO) and an RSSO user group
- Write a policy that only matches passively identified users
- Explain FSSO DC agent and collector agent (polling) modes and their ports
- Configure an FSSO agent connection and read its status and user list
The tasks
- Start the lab
- Active versus passive
- Receive RADIUS accounting (RSSO)
- A policy for passively identified users
- Watch identities arrive and leave
- Prepare FSSO for Active Directory
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.
Every link, as text
- FGT1
port1to INETeth0 - FGT1
port2to LAN (network) - PC1
eth0to LAN (network) - H1
eth0to LAN (network) - FGT1
port3to SRV1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| FGT1 | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| INET | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| PC1 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 2,048 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| SRV1 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
FortiGate NSE 4 guided labs.Open
12 - Passive authentication - RSSO and FSSOand 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
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.