Authentication fails in VCF Operations and VCF Operations for Logs for cross-domain Active Directory users within universal groups
search cancel

Authentication fails in VCF Operations and VCF Operations for Logs for cross-domain Active Directory users within universal groups

book

Article ID: 428285

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • AD users from different sub domains that are added to a universal group are unable to log in to VCF Operations using vIDB
  •  In VCF 9.0, Active Directory users from external subdomains are excluded from the vIDB synchronization process. Because vIDB fails to discover and import these accounts, the affected users are unable to authenticate.
  • The following UI error is displayed during cross-domain AD login attempts in VCF Operations for Logs: "401 Not Authorized Sorry, you are not authorized to view this page"
  • In VCF operations for Logs you may see the following error in /storage/core/loginsight/var/ui_runtime.log :  
    [2026-03-02 12:01:29.268+0000] ["https-openssl-apr-443-exec-10"/###.###.###.### ERROR] [com.vmware.loginsight.web.actions.settings.UsersActionBean] [Error generating AD Group autocomplete list] com.vmware.loginsight.rbac.RBACException: No groups with prefix ##### found in domain ######

Environment

  • VCF Operations 9.0.x
  • VCF Operations for Logs 9.0.x
  • VCF Identity Broker 9.0.x

Cause

Because vIDB configures its LDAP base search path using the universal group's domain dn=, the membership search is confined to that specific subdomain and its descendants. Consequently, any group members belonging to external subdomains will not be discovered.

Resolution

Broadcom engineering is aware of this limitation. A permanent fix is available starting in the VCF 9.1 GA release.

Workarounds for VCF 9.0.x
If you cannot immediately upgrade, implement one of the following structural adjustments: 

  • Option 1: Provision the universal group within the root/parent domain. You can then populate this single group with user accounts gathered from all child subdomains.
  • Option 2: Establish a dedicated security group inside each individual subdomain. Once created, manually import every subdomain group into vIDB as separate identity sources.