Release Notes

Welcome to the January 29, 2020 release of the Cloud Access Connector for Google Cloud, AWS and On-Premises. This release includes the following fixes and update:

Users can set set the IPv4 address for the Cloud Access Connector for external connections.

Using the --external-pcoip-ip command, users can now set the IPv4 address for the Cloud Access Connector for external connections. If this value is not set it will be determined automatically. 

Equals sign (=) in service account passwords caused the Cloud Access Connector to not sync users/machines to CAM

An issue has been fixed that caused some of the Cloud Access Connector docker containers to crash if one of the service account's passwords had an '=' in it.

Fetching LDAPS Certificates succeeds even if some Domain Controllers don't support it

If the number of discovered Domain Controllers with LDAPS was not greater than the number of discovered Domain Controllers without LDAPS, the installation of the Cloud Access Connector would fail due to some logic it did to verify certificates. As long as one Domain Controller has LDAPS enabled, installation of the Cloud Access Connector will now succeed.

cam.teradici.com is now used to determine an external IP address

The Cloud Access Connector now makes use of cam.teradici.com to determine it's external IP. This removes the need to ensure network access is available to myip.dnsomatic.com or resolver1.opendns.com.