This article applies to Creative Cloud 2018 and older versions.
Creative Cloud expands on application functionality by providing access to various services, such as Assets, Adobe Fonts, and Behance. In many enterprises, a proxy server is implemented to restrict and control access to the Internet.
This article describes the various levels of support for Proxy environments in the Creative Cloud products.
In an enterprise environment, Creative Cloud Libraries must connect to localhost for the Libraries panel in applications to sync correctly. Therefore, if you're using Libraries, set localhost and 127.0.0.1 to bypass the proxy server for the enterprise environment.
On a Mac computer, if you're using Proxy Auto-configuration (PAC) or the Web Proxy Autodiscovery Protocol (WPAD), you must also enable the Exclude simple hostnames setting.
Note: This setting is required if you manually enter the proxy server URL or IP.
The following proxy configurations are supported on Mac and Windows:
The following proxy configurations are not supported:
The Creative Cloud desktop app and Creative Cloud Packager support remote pac files with basic authentication (pac files stored on remote server referenced by URL).
The Creative Cloud desktop app and Creative Cloud Packager do not support locally stored pac files.
NTLM authentication is not supported.
It is recommended that you only rely on HTTP and HTTPS proxies. SOCKS proxy is not supported in the Creative Cloud desktop app.
If your enterprise environment is configured to use a proxy server with basic authentication, the following behavior is observed.
If you are using the full functionality of the Creative Cloud, then your users are signing in via the Creative Cloud desktop app to license the software and use the services. When the Creative Cloud desktop app is first launched and detects a proxy in place, it prompts for credentials.
Enter the credentials for the proxy server and select to save. When the Creative Cloud apps launch, they query for a connection to the Internet. The apps recognize that the credentials are already stored by the Creative Cloud desktop app and, therefore, they use the credentials.
Users no longer receive any prompts from the applications to connect to the Internet, and all the functionality is unlocked.
The following application, however, has not fully integrated this support and the following behavior can be observed when in an authenticated proxy environment.
A user is prompted multiple times to enter credentials. When a user selects to save, the credentials dialog is suppressed and does not display during subsequent launches.
If you have an authenticated proxy environment, but don't have Creative Cloud desktop app installed, each application handles its proxy connection with varying consequences. Usually, a single prompt appears requesting proxy credentials. However, sometimes, multiple persistent dialogues appear at launch and when more functionality is accessed.
To bypass authentication, some proxy servers allow for whitelisting of domains. A comprehensive list is available in the Creative Cloud enterprise endpoints document.
If you are fully offline, then the applications fail gracefully, and do not prompt for any credentials to connect to the Internet. If end users try to access any online functionality, they are informed that they are offline. If end users try to access services, such as libraries that require the Creative Cloud desktop app, they are informed that they must install.
There are many functions within the products that lead to an Internet connection being requested. Some of these features are:
The Sync settings feature works in proxy environments when used in the latest versions of the following products: