Skip to main content
AEK
SuperUser
SuperUser
September 1, 2026
Question

FortiNAC, AD user cannot override itself if created by RADIUS

  • September 1, 2026
  • 4 replies
  • 95 views

HI FNAC admins

FortiNAC-F 7.2.9.

I have this scenario:

  1. A new AD users (not added to FNAC yet) connects to SSID managed by FNAC from a client having NAC agent
  2. FNAC adds it automatically to user DB (created from RADIUS connection) , and it adds it not as “Loaded from Directory”, but just like local user, and remains the same even after AD sync
  3. As it didn’t add it as “Loaded from Directory” it doesn’t match my UHP neither my access policy, so it is dropped in isolation
  4. So I have to remove the user manually and let it created by LDAP automatically after sometime

My question:

  1. Is there a way to force AD user override existing user created from RADIUS connection
  2. Otherwise is there a way just to preload all ad users to FNAC user DB even before any user connects
  3. Or any other flexible/automatic solution

4 replies

ebilcari
Staff
Staff
September 1, 2026

Normally, during authentication an LDAP query is performed to retrieve the user information and create the user account with the ‘Loaded from Directory’ status and all the user attributes.

Does this issue affect all or only specific users? Do the affected users have any special characters in their attributes? How is the user automatically created later on, do they later authenticate through the portal or the persistent agent?

Have you tried to reproduce the issue with these debugs on:

fnac # diagnose debug plugin disable DirectoryManager
fnac # diagnose debug plugin disable DirectoryAuthentication

There are a few similar issues reported for this firmware (like 1194498) but the fixes are included only in the other supported release branches.

As far as I know, there is no way to force user synchronization or preload directory users into FNAC. I'm also not certain how a manual CSV import would behave for users that are found in the directory. As a last resort they can be created manually, one by one in Users.

Emirjon
AEK
SuperUser
AEKAuthor
SuperUser
September 1, 2026

Hi Emirjon

Thanks for your feedback.

This happens only for “new” users (on PC with PA) that connect for the first time via WiFi before connecting via wire network. When I see new users I also confirm that we synced FNAC with AD before the test.

On the other hand if one “new” user connects for the first time on wire network before WiFi, the FNAC adds him as Directory user, that’s logic because the user is not added by RADIUS. And then if the same user connects via WiFi all works just fine. So the issue is decided on the very first connection of the new user, if it is WiFi or wire.

AEK
ebilcari
Staff
Staff
September 2, 2026

Are the WiFi hosts being registered through Dot1x Auto Registration? When the host is authenticated only through RADIUS, is the "Registered To" attribute populated? Does the domain and username format used during the RADIUS authentication match the LDAP configuration? If Dot1x Auto Registration is not being used on the SSID, is the user information populated in the "Logged On" attribute?

You can also check from the CLI for the user attributes if they are partially synchronized:

fnac:~$ dumpuserrecords -first 'gimi'
        UserRecord:
          Landscape = 92023029761 00:15:6D:00:00:01
          ID = 6
          Role = NetworkUser
          Type = UserRecord
          Admin Profile DBID = 0
          Directory Policy =
          DN = CN=gimi,OU=Usr,DC=eb,DC=eu
          Position = Shef IT
          Email Address = gimi@eb.eu
          First Name = gimi
          Last Name = null…...

Emirjon
AEK
SuperUser
AEKAuthor
SuperUser
September 3, 2026

I checked dot1x in ssid and it is off (default), but actually the tests I made were on an already registered host, and here it is clear that the issue is not in the host registration but in the user registration. And I confirm the user information populated in the "Logged On" attribute.

Know that the PA is installed on the PC, and the PA should tell FNAC that the AD user is logged in right, and I suppose it does already, but since this is a new user, I guess FNAC couldn’t create it as “Loaded from Directory” since the same “user id” has been created by RADIUS authentication not as “Loaded from Directory”, I guess FNAC just didn’t allow itself to overwrite it, right? And once I delete the user, FNAC creates it few minutes later as “Loaded from Directory”. That’s what I want to do automatically if possible.
Regarding domain & user format in RADIUS authentication, I just used the correct AD username and it worked, I didn’t specify the domain with the username. For info I’m using RADIUS proxy, and I want to avoid local RADIUS/Winbind.
I’ll try run the provided command and will share the output.
Thanks again, Emirjon.

AEK
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!