I'm not aware of any particular issues with FortiTokenCloud related to FortiClient of any sort.
For FortiClient, the tokens should be treated much the same whether they are Cloud tokens, mobile tokens or hardware tokens.
It's primarily up to the FortiGate or FortiAuthenticator to handle token prompt and associate users with tokens (and then require them in VPN or other authentication context). Could you share some more information as to your FortiGate side setup?
- what firmware version are you using?
- is this IKEv2 IPSec? There were some issues with tokens for remote users in some firmware versions if I remember (don't think 7.2.3 was one of them though)
- have you tested SSLVPN to see if this is an IPSec-specific issue?
- what exact error are you getting? Does the tunnel setup break down at a specific point (and works without token)? Is the issue restricted to Cloud tokens, or does it also crop up with mobile tokens? (For testing, you should have two free mobile tokens on your FortiGate/FortiAuthenticator you can try instead of a Cloud token)
As mentioned above, from FortiClient perspective it shouldn't really matter what type of token the user has; it should only matter if a token is requested or not, and FortiClient shouldn't really behave any differently for the different token options.
+++ Divide by Cucumber Error. Please Reinstall Universe and Reboot +++