Created on 06-05-2015 03:09 AM Edited on 01-05-2025 09:54 PM By Jean-Philippe_P
Description |
This article describes the first steps to take in case of FortiToken activation failure. If the configuration has been migrated from another unit, the tokens will not work unless they are completely removed first and then re-imported.
|
Scope | FortiGate. |
Solution |
Step 1: General view:
exec ping fds1.fortinet.com
exec ping directregistration.fortinet.com show system central-management The above servers must be reachable from the FortiGate. When a FortiManager manages the system, skip the next steps as the tokens should be provided by FortiManager itself.
Step 2: Current status check: diag fortitoken info
diag test application forticldd 7 show user fortitoken Step 3: Run the following command: show full | grep -f FTK
Step 4: Turn on activation debugging: diag debug reset
diag debug console time en
diag debug app forticldd 255
diag fortitoken debug enable
diag debug enable
diag debug info
The FortiToken-200 is activated through the FortiGuard network and is locked upon first activation (one-time activation lock). If the token's lock was released recently, there is only one chance to activate and catch an error if an issue occurs.
Step 5a: If the Token was deleted as per step 3a., run only this command (and skip the activation): config user fortitoken
edit <FortiTokenSN> end Step 5b: Otherwise, activate it:
exec fortitoken activate <FortiTokenSN>
diag fortitoken info | grep -v active
All tokens should be active and should have the seed in config:
diag fortitoken info
show user fortitoken disable debug diag debug reset diag debug disable To verify whether the FortiToken activation code is being sent over e-mail, collect the below command output:
sh system email-server
diag debug reset
diag debug appl alertmail -1
diag debug enable
After running the above commands, trigger an activation request and analyze the output. This is done by selecting 'Send Activation Code' under User&Authentication -> User Definition -> Edit the user.
It's important to understand that the troubleshooting steps above primarily concern themselves with the activation of a token when binding to a specific user. If the problem relates to attempting to activate additional FortiToken Mobile on the FortiGate and errors are seen in the GUI or CLI like the examples below, follow the additional troubleshooting steps further below.
Step 1: Run the FortiToken debug.
diagnose debug reset diagnose debug console time enable diagnose fortitoken debug enable diagnose debug enable
Step 2: Get the logs and analyze the output for possible errors as seen below.
[641] fds_ctx_set_addr: server: 173.243.138.68:443
[188] fds_svr_default_pickup_server: fdni: 173.243.138.68:443 [337] fds_send_reply: Sending 1005 bytes data. [361] fds_send_reply: send reply failed: req-1, Connection refused { "d": { "__type": "SoftToken.ActivationLicenseRequest", "__version": "4", "license_activation_code": "DA8C-0508-1F31-4CF7-C990", "serial_number": "FG4H0ETB20900993", "__device_version": "6.0", "__device_build": "6325", "__clustered_sns": [ { "sn": "FG4H0ETB20900993" }, { "sn": "FG4H0E5819900260" } ] } } ftm_fc_comm_recv_response[477]:receive packet from forticare success. {"d":{"__type":"SoftToken.ActivationLicenseResponse","__version":"4", "serial_number":"FG4H0ETB20900993", "__device_version":"6.0","__device_build":"6325","__clustered_sns":[{"sn":"FG4H0E5819900260","error":null},{"sn":"FG4H0ETB20900993","error":null}],"license_activation_code":"DA8C-0508-1F31-4CF7-C990","license":"","tokens":null,"result":0,"error": {"error_code":14,"error_message":"forticare license expired"}}} ftm_fc_command[564]:received error from forticare [-7564] import fortitoken license error: -7564 Look for the error messages as shown on the log above 'error_message':
error_message":"forticare license expired"
This log indicates the license code entered is expired. The solution is to get a new license code and to register it on the FortiGate.
{"__type":"SoftToken.ActivationLicenseResponse","__version":"4", :"xxxxxxxxxxxxxxxx","license":"","tokens":null,"result":0,"error":{"error_code":10, "error_message":"forticare license card not found"}}}
Refer to the solution in the article: Technical Tip: 'FortiCare license card not found'.
Related article: Technical Tip: Migrating users and FortiTokens to another FortiGate/FortiAuthenticator |
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 2025 Fortinet, Inc. All Rights Reserved.