BugZero | VMware vCenter BugID d8a61718fda7 - Adding Identity Provider users to a local Single S...

VMware vCenter - Defect ID: d8a61718fda7

Adding Identity Provider users to a local Single Sign-On group fails with the error No principal with specified name exists

VMware vCenter - Defect ID: d8a61718fda7

Adding Identity Provider users to a local Single Sign-On group fails with the error No principal with specified name exists

Last updated on January 12th, 2026

BugZero Risk Score
0.0 Coming soon

Overall: N/A

Severity: N/A

Community: N/A

Lifecycle: N/A

What is the BugZero Risk Score?

VMware vCenter Integration

Learn more about where this data comes from

VMware vCenter Integration

Learn more

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

Learn more

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Learn more

Bug Details

Status: Resolved
Impact Category: vCenter and vSphere Client Issues
Workaround Available:
Views: 1

Description

Disclaimer

A custom bug ID has been generated as the vendor did not provide one: d8a61718fda7

Overview

In some cases, when you use the vCenter linking capability under Infrastructure Operations > Configurations in VCF Operations, adding an Identity Provider user to a local Single Sign-On group in a vCenter instance might fail with the error: No principal with specified name exists .

Bug URLs

https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/release-notes/vmware-cloud-foundation-9-0-1-release-notes/vcenter-9-0-1-0000.html

Change history

2025-12-01 changed to Resolved

Top VMware vCenter Defects

Defect ID: PR-3026630
You see error messages when try to stage vSphere Lifecycle Manager Images on ESXi hosts of version earlier than 8.0
Defect ID: f24a2d043b60
A remediation task by using vSphere Lifecycle Manager might intermittently fail on ESXi hosts with DPUs
Defect ID: PR-3434710
After upgrading to vSphere 8.0 Update 3, Single Sign-On (SSO) users in Azure Active Directory groups get a "namespaces is forbidden" error when using kubectl
Defect ID: PR-3565605
The syslog configuration for the Workspace ONE Access service points to a wrong directory referring the former name VMware Identity Manager
Defect ID: PR-3417930
A fresh install of vCenter by using the CLI installer might fail due to a rare race condition

Ready to prevent the next vendor outage?

Get a demo

VMware vCenter - Defect ID: d8a61718fda7

Adding Identity Provider users to a local Single Sign-On group fails with the error No principal with specified name exists

VMware vCenter - Defect ID: d8a61718fda7

Adding Identity Provider users to a local Single Sign-On group fails with the error No principal with specified name exists

Last updated on January 12th, 2026

BugZero Risk Score0.0 Coming soon

Bug Details

Disclaimer

Overview

Bug URLs

Links

Top VMware vCenter Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
0.0 Coming soon