VMware vSphere FortiAuthenticator OVA import error:

Issues detected with selected template.

User fail to activate the FortiToken Mobile token.

It displays:

FTM Server: FTM token Activation Code is invalid (40).

Device seems to have radacctd process crashes.

EAP-TLS is not working in Azure.

FortiAuthenticator RADIUS logs not logging properly.

EAP-TLS is not working using FortiSwitch and certificate bindings.

Local user with FortiToken Cloud and EAP-TLS authentication trying to reach FortiToken Cloud 9 times before authentication.

Port 1 configuration and routes deleted after network flaps between FortiAuthenticator cluster.

FortiAuthenticator 1000D cluster takes very long during failover and reboot. The disk monitor message says Exception in service: stoi.

VPN tunnel cannot be up after failover to a secondary FortiAuthenticator.

SFP port 5 and 6 on FortiAuthenticator 800F going down and requires reboot to fix.

FSAE is crashing with signal 6, seen in segfault.log.

Some of the users logged in a MAC device are unable to get user sessions listed on FortiAuthenticator.

Internal Server Error 500 when viewing RADIUS accounting sessions in Monitor section.

FAC's HSTS settings are not applied to facwad webserver.

FSSO user logins are not visible for user with large group membership.

SAML with FIDO authentication fails with Error occured during fido authentication.

Disallow saving settings when enabling Restrict token self-provisioning for specific groups with an empty group list.

Request password reset after OTP verification issue when feature is disabled.

FAC2KE PSU monitor widget does not accurately reflect the actual statuses of the PSUs on the device.

FortiToken hardware token is not assigned to the imported users if None is not selected in the sync rule.

Windows agent authentication using FortiToken Cloud with Email and SMS delivery option fails.

500 error after 2FA authentication with IAM user if the account field has a slash.