FortiManager 7.6.6 LDAP config from one VDOM showing up in another VDOM during install
Hey guys,
I've run into a weird issue and I'm not sure whether this is expected behavior, user error, or a possible FortiManager bug.
One of my colleagues recently added an LDAP configuration change on one of our FortiGate's VDOMs. When creating the object in FortiManager, the per-device mapping was specifically set to:
fg01 [VDOM1]
For context, the FortiGate has multiple VDOMs:
- root
- VDOM1
- VDOM2
- VDOM3
The strange part is that when I later try to install an unrelated change to the root VDOM, the LDAP configuration that was created for VDOM1 appears in the install preview for root as well. I wouldn't expect that to happen.
My first thought was that there might be a stale database entry under the root VDOM, so I checked:
Device Manager > Device & Groups > fg01 [root] > CLI Configurations > user > ldap
However, there are no records found.
To me, that indicates FortiManager should not be pushing any LDAP configuration to the root VDOM, yet the LDAP config from VDOM1 keeps appearing every time I perform an install.
I've also tried various CLI/database resync commands, but the behavior remains the same. The LDAP configuration continues to show up in the install preview despite not existing in the root VDOM's device database. This is also the same for VDOM2. For some reason VDOM3 is not affected.
Has anyone seen this before?
A few questions:
- Is this expected behavior with per-device mappings and VDOMs?
- Could this be a database synchronization issue within FortiManager?
- Is there another location where FortiManager could be storing this LDAP configuration that I'm overlooking?
- Any recommendations for troubleshooting this further?
Thanks!