Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Failed to add groups to the “CloudAdminGroup” during HLM (55867)

Last Updated: 4/4/2024Categories: TroubleshootingTotal Views: 3262Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You are trying to add groups to the “CloudAdminGroup” by using the “Edit Admins” option in the Linked Domains screen.

After searching the group and adding it, the process fails with error: “Setting administrator failed with reason: Failed to add groups. Contact support for further assistance”

Identity Source Type of “Open LDAP” has been added to the Vcenter.

In the HLM logs you see errors like:

[2018-05-21T19:50:20.839Z pool-3-thread-824 vmc.local 861c2492-d059-4792-b4a4-c1805bf0a0f5 ERROR com.vmware.identity.idm.server.IdentityManager] Not allowed: awsadmins@xx objectId is null
[2018-05-21T19:50:20.839Z pool-3-thread-824 vmc.local 861c2492-d059-4792-b4a4-c1805bf0a0f5 ERROR com.vmware.identity.idm.server.IdentityManager] Failed to add group [awsadmins@xx] to group [CloudAdminGroup] in tenant [vmc.local]
[2018-05-21T19:50:20.839Z pool-3-thread-824 vmc.local 861c2492-d059-4792-b4a4-c1805bf0a0f5 ERROR com.vmware.identity.idm.server.ServerUtils] Exception 'java.lang.IllegalArgumentException: Not allowed: awsadmins@xx objectId is null'
java.lang.IllegalArgumentException: Not allowed: awsadmins@xx objectId is null
at com.vmware.identity.idm.server.IdentityManager.validateObjectIdNotNull(IdentityManager.java:5876) ~[vmware-identity-idm-server-7.0.0.jar:?]

Note: The above log extract is just an example and the values may change depending upon your environment

Cause

We have this issue because the group that is being added to the “CloudAdminGroup”  has its objectId as null.

The group might be created without a GID i.e. group SID is missing and you would need to verify the group attributes in the LDAP directory.

Resolution

Make sure the LDAP server being used is supported by Vsphere. Please refer OpenLDAP schemas supported in VMware vCenter Single Sign-On (2064977) for details around supporting OpenLDAP as an identity source.
Currently, vCenter Single Sign-On supports the use of OpenLDAP as an identity source only if it satisfies all of these requirements:

The OpenLDAP schema is RFC4519 compliant.

All users have an objectClass of inetOrgPerson.

All groups have an objectClass of groupOfUniqueNames.

All groups have a group membership attribute of uniqueMember.

All users and group objects have entryUUID configured (The objects have a unique GUID and should not be changing)

Note:
The above configuration is required for adding users or groups from OpenLDAP to any group or role apart from vSphere.local.
In vSphere 5.5a and later, entryUUID is no longer a required attribute for OpenLDAP users to authenticate. However, it still remains a requirement for users/groups to add them into vsphere.local groups. Users or objects that are deleted and recreated in the LDAP tree without preserving entryUUID may remove the users from vsphere.local groups.
If any of these requirements are missing or if the schema is non-compliant, the OpenLDAP identity source is unsupported with vCenter Single Sign-On.

If the OpenLDAP server is supported and meets all the requirements mentioned in the associated KB (2064977), make sure the group object has a unique SID.
Once you assign it a unique ID, try adding the group again and the issue should be fixed.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant