HA cluster and FortiAuthenticator GUI does not reflect correct HA status when the primary fails and the secondary becomes the new primary.

Problem setting static IP address on a FortiAuthenticator-VM installed on a XenServer.

SSL connection fails in case of the certificate expired issue is not explicit enough.

Local cert for the GUI rejected despite SAN field.

Octet/ASCII conversion for all RADIUS attribute-value pairs.

SCEP errors displayed when there is no enrollment request from the client (FortiGate).

Unable to import all FTK hardware tokens from the same purchase order; need to add them all manually.

FortiAuthenticator does not check if the signature of CSR is valid.

Unable to install FortiAuthenticator-VM-HV 6.2.0 on server 2012 R2.

Error when importing a remote LDAP user.

Nutanix AHV KVM based Hypervisor FortiAuthenticator upgrade from 6.0.4 to 6.1.x fail hangs on "Waiting for Database".

Allow deletion of the expired user and the local service certificates.

SCEP - Encryption/hash compatibility with clients.

When FortiAuthenticator has a RADIUS client set as a subnet, RADIUS accounting disconnect messages are not sent.

Unable to provide publisher details/assign code signing certificate to the Smart Connect profile.

Sponsor accounts can add guest user accounts to non-guest groups.

FortiAuthenticator Syslog FSSO injects speech mark (") around external user and group fields where none exist in the raw log.

FortiAuthenticator limits various user fields to 30 characters, causing remote LDAP sync failures unexpectedly.

Raid widget is showing wrong status.

High CPU utilization by wmid process.

Unable to import users by group membership from OpenLDAP when a group is added in an OU.

Connection between FortiAuthenticator and the Active directory crashes; customer cannot access the device.

SCEP request by certmonger cannot be recognized by automatic enrollment request.

Corp FortiAuthenticator SAML login failure to mantis after VPN is disconnected.

HTTP services - CRL Downloads (/cert/crl) enabled, but we still get warning that HTTP access needs to be enabled.

AP HA primary cannot change mgmt interface access configuration, and the option does not sync from the primary either.

Script errors on logging in to Microsoft Teams using SAML (FortiAuthenticator as the idP).

FortiAuthenticator A-P running in v6.2.1 does not sync with the secondary unit pre-authentication warning message, CLI and GUI timeout.

Smart Connect should not require user to select the OS.

Some users are not receiving push notification prompt on their mobile phone.