{"id":76856,"date":"2023-06-05T13:11:02","date_gmt":"2023-06-05T17:11:02","guid":{"rendered":"https:\/\/jumpcloud.com\/?post_type=support&p=76856"},"modified":"2023-06-05T13:11:02","modified_gmt":"2023-06-05T17:11:02","slug":"configure-vmware-vcenter-to-use-cloud-ldap","status":"publish","type":"support","link":"https:\/\/ti-1.jumpcloud.com\/support\/configure-vmware-vcenter-to-use-cloud-ldap","title":{"rendered":"Configure VMware VCenter to Use Cloud LDAP"},"content":{"rendered":"\n
A common request from JumpCloud Administrators is to\u00a0integrate JumpCloud’s LDAP-as-a-Service with VMWare vCenter.\u00a0JumpCloud’s LDAP-as-a-Service is\u00a0RFC2307 compliant, while vCenter currently supports RFC4519.<\/p>\n\n\n\n
RFC4519 Schema:<\/p>\n\n\n\n
This leads to Users working as expected for inetOrgPerson for JumpCloud.\u00a0However, User Group functionality for groupOfNames with JumpCloud will not work<\/strong>.\u00a0You can set up\u00a0LDAP to JumpCloud with vCenter, but you will need\u00a0to set up local vsphere.local User Groups and add JumpCloud LDAP Users as members.<\/p>\n\n\n\n This is an issue with the way that VMware has developed their OpenLDAP configuration by using the 4519 Schema instead of RFC2307. Please reach out to VMware to put in a feature request to support RFC2307, as this is not something JumpCloud can change or resolve with their LDAP Client in vCenter.<\/p>\n\n\n\nConfiguring vCenter with JumpCloud LDAP<\/h2>\n\n\n\n