I had the same issue with my 300C' s.. A tech milled around asking for this and that log for an entire day. Next day he was out and I spoke with another guy. He checked 1-2 things then put me on hold for a sec... He came back and said this is A KNOWN ISSUE with 5.2!!
The temp fix is to put the password and token # all in the password line with no spaces. It will work.
So if my pass is " He8mycode!" and my token is showing 12345. Use " He8mycode!12345" as the password and it works.
Said fix is slated for 5.2.1 Aug 15 2014.
This is the 2nd glaring, in your face, you can' t miss it, firmware issue I' ve seen and I' ve only had FG for less than 1 year now!
My 200D' s traffic stats are all messed up in every view. WAN interface shows BITS of traffic, and apps like YouTube show BITS and BYTES of traffic... WRONG.. I was told someone typed in the wrong network processor or something and it messed up all the stats... That has been broken for longer than I' ve had my 200D and only just got fixed in 5.0.8 and 5.2 so they say..
I really like FN products.. but their QA is freeken out to lunch.. how could you miss the traffic only logging bytes... when you first log into the GUI the first thing you see is WAN interface... did you not notice no traffic in your test? Did you test the FortiToken in 5.2? You could NOT have... it' s impossible.
300E x3, 200D, 140D, 94D, 90D x2, 80D, 40C, handful of 60E's.. starting to loose track.
Over 100 WiFi AP's and growing.
FAZ-200D
FAC-VM 2 node cluster
Friends don't let friends FWF!