FortiAuthenticator: Unassigned FortiTokens in pending status

[dsimsik]

Hello.

We have 200 FortiTokens registered with FortiAuthenticator (FAC).

There is a single synchronization rule, to synchronize users from LDAP server (ActiveDirectory). The rule automatically assigns a free FortiToken to new user, when he is found in AD and pulled to RemoteUsers list in FAC.

The problem is, there are about 120 tokens already assigned and all remaining tokens are in pending status, even though no user has been assigned to them yet. If I login to FAC, I can manually refresh the status of tokens, and it always free up some (not all!) unused tokens.

What is the reason behind it? Why are tokens being pushed to the pending status without any assignment?

[ebilcari]

Are all the tokens in the Pending status not showing a User? What is the firmware version that is currently running?

You can check the token assignment history in the Logs (using the serial):

[dsimsik]

Hi Ebilcari.

I have checked logs and found out 2 users with wrong email addresses. The log messages repeated every hour (the sync rule timer). Customer fixed the addresses in AD, I cleared the pending status of the tokens and for next 48 hours none of the unassigned tokens went to the pending status. This solved the issue and thanks for pointing me to the logs.

Anyway, I found it strange,that FAC pulled the users from AD, assigned them a token (which has 30 days activation period), then failed to send the activation emails and decided to solve this automatically by assigning another token within the synchronization period just to fail again and again...

[ebilcari]

Thank you for sharing your findings. This seems like a strange behavior, kindly open a ticket with TAC support to investigate it further.