Download Fortinet.NSE6_FAC-6.4.VCEplus.2025-01-03.32q.vcex

To deploy three FortiAuthenticator devices to provide active-passive HA at headquarters, with geographically distributed load balancing, the role settings would be:One standalone primary, which acts as the master device for HA and load balancing One cluster member, which acts as the backup device for HA and load balancing One load balancer, which acts as a remote device that forwards authentication requests to the primary or cluster member deviceReference: https://docs.fortinet.com/document/fortiauthenticator/6.4.0/administrationguide/906179/high-availability#ha-and-load-balancing

To allow members of only specific AD groups to participate in FSSO with their corporate FortiGate firewalls, the administrator can configure SSO groups and assign them to FortiGate groups. SSO groups are groups of users or devices that are defined on FortiAuthenticator based on various criteria, such as user group membership, source IP address, MAC address, or device type. FortiGate groups are groups of users or devices that are defined on FortiGate based on various criteria, such as user group membership, firewall policy, or authentication method. By mapping SSO groups to FortiGate groups, the administrator can control which users or devices can access the network resources protected by FortiGate.Reference: https://docs.fortinet.com/document/fortiauthenticator/6.4.0/administrationguide/906179/single-sign-on#sso-groups

FortiClient SSO Mobility Agent is a FSSO discovery method that transparently detects logged off users without having to rely on external features such as WMI polling. FortiClient SSO Mobility Agent is a software agent that runs on Windows devices and communicates with FortiAuthenticator to provide FSSO information. The agent can detect user logon and logoff events without using WMI polling, which can reduce network traffic and improve performance.Reference: https://docs.fortinet.com/document/fortiauthenticator/6.4.0/administrationguide/906179/single-sign-on#forticlient-sso-mobility-agent

TOTP stands for Time-based One-time Password, which is a type of OTP that is generated based on two pieces of information: time and seed. The time is the current timestamp that is synchronized between the client and the server. The seed is a secret key that is shared between the client and the server. The TOTP algorithm combines the time and the seed to generate a unique and short-lived OTP that can be used for two-factor authentication.Reference: https://docs.fortinet.com/document/fortiauthenticator/6.4.0/administrationguide/906179/two-factor-authentication#totp

Reference: https://www.fortinet.com/content/dam/fortinet/assets/data-sheets/fortitoken.pdfHOTP stands for HMAC-based One-time Password, which is an OATH-based standard to generate event-based OTP tokens. HOTP uses a cryptographic hash function called HMAC (Hash-based Message Authentication Code) to generate OTPs based on two pieces of information: a secret key and a counter. The counter is incremented by one after each OTP generation, creating an eventbased sequence of OTPs.Reference: https://docs.fortinet.com/document/fortiauthenticator/6.4.0/administrationguide/906179/two-factor-authentication#hotp

Realms are a way to delegate user accounts, user groups and permissions per domain when they are authenticating on a single FortiAuthenticator device. A realm is a logical grouping of users and groups based on a common attribute, such as a domain name or an IP address range. Realms allow administrators to apply different authentication policies and settings to different groups of users based on their realm membership.Reference: https://docs.fortinet.com/document/fortiauthenticator/6.4.0/administrationguide/906179/user-management#realms

Adaptive Authentication is a feature that allows administrators to bypass the need for two-factor authentication for users accessing from specific secured networks. Adaptive Authentication uses geolocation information from IP addresses to determine whether a user is accessing from a trusted network or not. If the user is accessing from a trusted network, FortiAuthenticator can skip the second factor of authentication and grant access based on the first factor only.Reference: https://docs.fortinet.com/document/fortiauthenticator/6.4.0/administrationguide/906179/authentication-policies#adaptive-authentication

When deploying FortiAuthenticator for portal services, such as guest portal, sponsor portal, user portal or FortiToken activation portal, the network configuration must allow specific ports to be open between FortiAuthenticator and the authentication clients. These ports are:TCP 80 for HTTP access TCP 443 for HTTPS access TCP 389 for LDAP access TCP 636 for LDAPS access UDP 1812 for RADIUS authentication UDP 1813 for RADIUS accounting Reference:https://docs.fortinet.com/document/fortiauthenticator/6.4.0/administrationguide/906179/portal-services#network-configuration

One possible cause of the issue is time drift between FortiAuthenticator and hardware tokens. Time drift occurs when the internal clocks of FortiAuthenticator and hardware tokens are not synchronized. This can result in mismatched one-time passwords (OTPs) generated by the hardware tokens and expected by FortiAuthenticator. To prevent this issue, FortiAuthenticator provides a time drift tolerance option that allows a certain number of seconds of difference between the clocks.Reference: https://docs.fortinet.com/document/fortiauthenticator/6.4.0/administrationguide/906179/two-factor-authentication#time-drift-tolerance

An OCSP responder URL in an end-entity certificate is used to designate a server for certificate status checking. OCSP stands for Online Certificate Status Protocol, which is a method of verifying whether a certificate is valid or revoked in real time. An OCSP responder is a server that responds to OCSP requests from clients with the status of the certificate in question. The OCSP responder URL in an end-entity certificate points to the location of the OCSP responder that can provide the status of that certificate.Reference: https://docs.fortinet.com/document/fortiauthenticator/6.4.0/administrationguide/906179/certificate-management#ocsp-responder