<user>@example.com) which differs from the domain added to vIDB (example.net)VMware Cloud Foundation Operations for logs 9.0.1.0
VCF Identity Broker 9.0.x
An authentication conflict occurs when you enable both vSphere SSO (VIDB) and native AD concurrently. The system queries your native AD configuration first for group enumeration and user resolution. This process fails if your native AD integration lacks visibility into the specific domain or trusted forest, which prevents the vSphere SSO authentication sequence from completing.
You see the following authentication errors in the /storage/var/loginsight/runtime.log when both are enabled:
[2026-03-12 16:37:15.660+0000] ["CheckPerformer-thread-1"/##.###.###.### WARN] [com.vmware.loginsight.prodcheck.lib.ActiveDirectoryCheck] [Wasn't able to authenticate to active directory]
com.vmware.loginsight.commons.exceptions.AuthenticationException: Unable to validate Active Directory credentials. Please check your Active Directory DNS name, port, and SSL settings as well as your username and password.
[2026-03-12 16:39:38.708+0000] ["https-openssl-apr-443-exec-7"/##.###.###.### ERROR] [com.vmware.loginsight.web.actions.settings.UsersActionBean] [Error creating group]
com.vmware.loginsight.commons.exceptions.AuthenticationException: Unable to validate Active Directory group. Please check your Active Directory DNS name, port, and SSL settings as well as your username and password.
2026-03-12 16:45:49.212+0000] ["https-openssl-apr-443-exec-6"/##.###.###.### INFO] [com.vmware.loginsight.aaa.ad.ActiveDirectoryAuthenticator] [Failed authentication attempt for parsed users [ `[EMAIL]`] ] in domain [ `[`[HOSTNAME]` ]]
com.vmware.loginsight.commons.exceptions.AuthenticationException: Invalid or untrusted domain '`[`[HOSTNAME]`'.
Engineering is aware of this issue and is working on a resolution for an upcoming release.
To work around this issue, you can use one of the following two options:
Option 1: Disable Native Active Directory (Recommended) If you do not strictly require the native Active Directory integration, you can disable it to allow your vSphere SSO groups to synchronize successfully.
Disable the native Active Directory configuration within VCF Operations for Logs.
Rely exclusively on your vSphere SSO (VIDB) configuration (which can have AD configured as its own identity source) for user authentication and group management.
Option 2: Add Users Individually If you must keep both native AD and vSphere SSO enabled concurrently, you must bypass group-based provisioning and add users individually.
Log in to the VCF Operations for Logs UI.
Expand the main menu and navigate to Management > Access Control.
Select Add User.
Enter the user details manually, ensuring you assign the correct domain (i.e., @example.com).
Save the entry and have the user attempt a fresh logon.