You are correct about it being built on the Chromium framework, which is why I identified the following variables as being incorrectly set:
CefSettings.UserAgent
CefSettings.product_name
CefSettings.product_version
Our enterprise network does not allow Chrome version 25 on our network for security reasons, so by Creative Cloud using the default string of "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.68 Safari/537.22" it causes our proxy to block the traffic. Allowing Chrome 25 on our network is simply not an option for security reasons.
Talk to other Adobe developers, they all accurately set their application user agent string to a string that correctly identifies itself. Just open a bug report to set the variables above to something like "Creative_Cloud_1.8.0.447" This solves the problem and gets your application away from using a string that matches a severely outdated version of Google Chrome.
As for the outdated case, I've opened a new one with my adobe account, and I can be contacted through that case #0214440666. All I want you to do is open this as a bug report, and have a developer set the variables for user agent string in the next Creative Cloud release.
