Forticient 7.4.5 Bug 1208862 - MFA and Entra ID

[futureweb]

Hi,

I couldn’t find any additional information or discussion about the bug mentioned in the 7.4.5 release notes.

I’m currently doing a new EMS deployment connected to Microsoft Entra ID and I’m having issues with Invitation Code registration. The Invitation Code gets accepted, but the client never completes registration (it just keeps loading). EMS logs don’t show much.

I tested disabling MFA for one user. After some time, I was able to successfully register one device using an Invitation Code, but I still could not register a second device with the same user (same tenant, same EMS settings, devices provisioned the same way via Intune).

Because EMS can resolve and display the Entra ID domain user correctly for the device that registered, I assume the Entra connection/setup itself is basically working.

Could this behavior be caused by the following known issue?

1208862
Entra ID user verification fails if MFA is made compulsory on Entra ID side.

If yes: is there any ETA for an update or hotfix that addresses this?

Also: I’m deploying the FortiClient via Intune. I couldn’t find clear documentation whether Invitation Codes are expected to work reliably when using an Entra ID domain connection and the user is logged in via Entra on the Device, or if you have to provide invitation codes anyway to login (when it works). Or could this be related to the same issue?

When I am not forcing user (none) - it worked through intune, but I do not want to deploy this way. 

Thanks,

Patrick

[AEK]

Hi Patrick

Invitation can be disabled, so you can register client without invitation code if the client is domain joined.

Also as far as I know MFA is not (yet?) supported with user verification on registration.