Description | This article describes that under 'User & Authentication', when changing the user's two-factor authentication from FortiToken Cloud to FortiToken, an error message 'CLI internal error' can show up. |
Scope | FortiGate. |
Solution |
The error may show up when there is no FortiToken cloud license, and the trail license has not been activated. To confirm, run debug on FortiCloud using the command below:
diagnose debug application forticldd 255 diagnose fortitoken debug enable diagnose debug enable
Try to change the token again, then check the debug output, and look for the message similar to the one below:
{ "d": { "__type": "SoftToken.ProvisionRequest", "__version": "4", "__device_version": "7.0", "__device_build": "2360", "serial_number": "FGVMSLTM12121212", "__cluster 2024-08-14 11:20:42 ftm_fc_comm_recv_response[266]:receive packet success. {"d":{"__type":"SoftToken.ProvisionResponse","__version":"4","serial_number":"FGVMSLTM12121212","__device_version":"7.0","__device_build":"2360","__clustered_sns":[]," 2024-08-14 11:20:42 ftm_cfg_update_token_provision[684]:Set token FTKMOB123456789 to provisioning
This means when there is no FortiToken cloud license, FortiGate is unable to communicate to FortiCloud to update the token provision status. The solution is to activate the trial license for FortiToken Cloud, then FortiToken Coud communication will be successful, and the error will disappear. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.