Description | This article describes the issue when it is impossible to assign a new token to the user after the upgrade to v6.6.0/v6.6.1. |
Scope | FortiAuthenticator v6.6.0, v6.6.1. |
Solution |
After upgrading the FortiAuthenticator to version 6.6.0/6.6.1, the following error can occur during assigning FortiToken.
Unable to provision token FTKMOBxxxxxxx: Unknown error. Your changes have been rolled back. Please try again later.
FTM provision error: problem with SSL comm layer: failed to recv response header: SSL communication layer error
Failed to send registration update (code = -14)
FGD SMS: problem with SSL comm layer
Also visible from the logs:
2024-05-27T14:42:58.717015+08:00 FortiAuthenticator gui[16524] debug fac.home.www-data.fac.fac.apps.fac_auth.clibs __init__ 140249236948672 Token provisioning request is from FAC.
Check if FortiAuthenticator can ping fortitokenmobile.fortinet.com:
exe ping fortitokenmobile.fortinet.com
For the solution, follow the next steps, re-uploading the VM license will solve the issue:
Note: The license can be found in the Support portal. Ensure the NTP is enabled and the time is correct. |