This article describes how to configure ZTNA Session Based Authentication with MFA Token.
During this setup, it was necessary to deploy the Session based form authentication with MFA.
This document is for log in with support for MFA (FortiToken).
This type of Session/form based authentication requires MFA and allows users to log in to internal resources.
This can be applied to local and remote users.
1) From the client machine, ensure it is able to resolve the domains and the portal domain:
2) It is possible to use LDAP user or local user with FortiToken:
- Enable 2FA with Token or use Local User Group with 2FA as per lab test below:
Username is abcd
Usergroup is LocalEMS
3) Configure ZTNA Authentication Scheme.
If using LDAP:
# config authentication scheme
If using Local User:
These are required:
set method form
4) Configure ZTNA server as per the diagram above.
5) Create an access proxy virtual host that points to the ZTNA access proxy.
The client will be redirected to this page for form authentication:
6) Enable auth-portal on the access proxy and point it to the virtual host:
7) Finally Create a ZTNA rule to allow the flow.
- It possible to use the ZTNA tagging as well to create matching:
1) Test local local user with a Token prompt.
Saga-kvm24 # diag test authserver local LocalEMS abcd xxxxxx
2) Ensure FortiClient is connected to the EMS telemetry and gets the right tag assigned.
3) Access the website to trigger the authportal site.
- Ensure Certificate gets prompted for the FortiClient <> EMS cert authentication portion:
It will be redirected to the Auth Portal Page:
Apply the credentials and Token and it will bring the request to the backend webserver:
Successfully able to load internal Webserver:
# diag debug application sslvpn -1
# diag endpoint record list x.x.x.x
# diag firewall dynamic list
# diag wad debug enable cat all