VMware vCloud Automation Center 6.0.1.1 released

VMware released an update to vCloud Automation Center 6.0.1 at May 1.

Release 6.0.1.1 contains just fixes, no new functionality.

Release notes are here. 

download vCAC 6.0.1.1 here

What’s Been Fixed

The following issues have been resolved in vCloud Automation Center release 6.0.1.1:

OpenSSL issue for IaaS component regarding CVE-2014-0160 Heartbleed vulnerability
The 32-bit and 64-bit vCloud Automation Center Windows Guest Agents and the vCloud Automation Center PE Builder components have been updated to use OpenSSL 1.0.1g. While these components previously embedded OpenSSL 1.0.1c, they were not vulnerable to the Heartbleed issue and hence you are not required to recreate any templates that were created by using these components. Going forward it is recommended to use the updated versions of these components to avoid any confusion on whether or not these newly created templates are vulnerable to the Heartbleed issue.

OpenSSL issue for Identity Appliance regarding CVE-2014-0160 Heartbleed vulnerability
OpenSSL version for Identity Appliance has been upgraded to 1.0.1g.

The Business Group tab of vCloud Automation Center throws exceptions
If the users try to access the Business Group tab of vCloud Automation Center, an exception Error has been caught, see event logs located on the vCAC server for detail or contact your system administrator for more information is displayed. A reboot of vCloud Automation Center is required to fix the issues for the affected users.

This issue has been fixed in this release.

Timeout error is displayed in vCloud Automation Center Entitlements page
Timeout occurs when you attempt to add groups to the Entitlements and an error message, Connection timeout. If the problem persists, contact your system administrator is displayed.

This issue has been fixed in this release.

The On Behalf Of field does not work in the Service Catalog
When you open a Tenant and navigate to Catalog and attempt to enter a username into the On Behalf Of field, the field is not updated and Loading� message appears continuously.

This issue has been fixed in this release.

Windows session authentication login fails and an error message is displayed because of VMware Client Integration Plug-in
If you attempt to use the Windows session authentication feature, it fails and an error message Windows Session Authentication login as failed as a result of an error caused by the VMware Client Integration Plugin is displayed. This issue occurred in Google Chrome 31.0.1650.63, Internet Explorer 9, and Firefox 25.0.1.

This issue has been fixed in this release for Google Chrome and Firefox browsers.

Unable to login when the UPN username does not match the SAMAccountName
If you configure active directory over LDAP provider, and select one of the UPN suffix to be an alias of the provider, vCloud Automation Center does not convert the eUPN using the alias logic and the original UPN is the eUPN of the user account.

This issue has been fixed in this release.

Active directory over LDAP provider is not returning vsphere.local groups for direct active directory user members
If you login with the active directory user, which is part of vsphere.local\administrators group, vCenter Server is not visible as part of the inventory.

This issue has been fixed in this release.

The vmidentity-firstboot of Windows based vCenter Server fails while trying to replicate with SSO in an embedded deployment
The Identity Service does not throw an exception if domain state is not compatible with the currently configured native active directory. This prevents IDM from starting up, log in to vCenter Server fails, and browsing of IDP information fail, and the system gets into unusable state.

This issue has been fixed in this release.

Native active directory times out when you try to see users in vCloud Automation Center
When you try to add the identity store for whichever native active directory domain that you want to use, for example sqa.local or sqa2k8.local, then you need to add administrators. At this point, native active directory might display an error message Connection timed out.

This issue has been fixed in this release.

Login to vCloud Automation Center fails when you try to login with SSO
When you try to login to vCloud Automation Center virtual appliance with SSO, the login fails and an error message Error received by LDAP client: com.vmware.identity.interop.ldap.WinLdapClientLibrary, error code: 10 is displayed.

This issue has been fixed in this release.

Advertisements

About Marcel van den Berg
I am a technical consultant with a strong focus on server virtualization, desktop virtualization, cloud computing and business continuity/disaster recovery.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: