vCloud Director 5.5 and a .local active directory domain

In the beginning of May i was informed by @encrypturlyf about an article “Why ABM Is Migrating from VMware to Hyper-V” published by www.cio.com. A few days back a customer of mine contacted me regarding the same article. Yes that was before i moved to Nutanix, i just haven’t had the time to put together a blog post:)
However, this really caught my attention and if looking on page 2 of the article you’ll find the following statement:

“We rolled out vCloud Director trying to implement a hybrid cloud, but vCloud Director wasn’t working for us because we had an Active Directory with .local at the end of it.”

The article doesn’t really explain what wasn’t working as it was supposed to in vCD when using an active directory domain using the .local format at the end of it.

The only thing i have seen in regards to .local AD domains in vCD 5.5 is that you can not log on to the vCD system portal ( https://vCD-FQDN/cloud ) or to any tenant ( https://vCD-FQDN/cloud/org/tenant ) using the vCD User name format used in e.g vCD 5.1 where you provide both AD user name and AD domain. I’m using a vcdx56.local domain and the following LDAP configuration in vCD 5.5:

Screen Shot 2014-05-20 at 15.49.02

I have put together a few screen shots showing you the User name specifications you can not use when using an AD with .local at the end of it:

Screen Shot 2014-05-13 at 23.49.10

Screen Shot 2014-05-13 at 23.49.35

Screen Shot 2014-05-14 at 00.04.53

All of the above login attempts to both the vCD system and vCD tenant portals will result in the following Authentication Error message:

Screen Shot 2014-05-13 at 23.49.55

The correct way to specify your vCD User name, at least when using an AD with the .local extension, is just the User name according to the below screen shot.

Screen Shot 2014-05-13 at 23.50.06

The above example will let you log in to the vCD system portal and to the tenants.

A comment to the post previously mentioned includes the following:

Please elaborate on what the impact of having .Local had to do with not getting vCloud Director to function properly. I’ve never heard of any issue like that with vCloud Director at least up until now. Thank you.” 

Unfortunately the question has not been answered but i really hope the reason for not using vCD wasn’t the potential login credential specification. I’ll update the blog post when i find out what exactly didn’t work when using the .local AD domain format.

4 pings

Comments have been disabled.