The Creative Cloud expands on application functionality by providing access to various services. Services such as Assets, 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.

Proxy requirements for Creative Cloud Libraries

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 need to also enable the Exclude simple hostnames setting.

Note: This setting is required if you manually enter the proxy server URL or IP.

For more information CC Libraries specific proxy configuration details, see Configure your proxy to work with Libraries and Configuration of proxy by a network administrator.

Supported proxy setting types

The following proxy configurations are supported on Mac and Windows:

  • Proxy settings using PAC URL, either with or without authentication
  • Auto Proxy Discovery (WPAD)
  • Basic authentication. If a user provides credentials in the Creative Cloud app, then Creative Cloud Libraries use the credentials. If the user does not provide credentials in the Creative Cloud app, then the Creative Cloud Libraries panel prompts the user for credentials.
  • Kerberos authentication is supported for Creative Cloud libraries and the Creative Cloud desktop app. However, Kerberos authentication is currently not supported for Creative Cloud 2015 products.

Unsupported proxy setting types

The following proxy configurations are not supported:

  • NTLM authentication
  • Local PAC file support

Support for pac files

The Creative Cloud desktop application and Creative Cloud Packager support remote pac files with basic authentication (pac files stored on a remote server and referenced by URL). 

The Creative Cloud desktop application and Creative Cloud Packager do not support locally stored pac files.

NTLM authentication is not supported.

Authenticated proxy environment with CC Desktop App and CC 2015 products

If your enterprise environment is configured to use a proxy server with basic authentication, the following behavior is observed.

If you are leveraging 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.
 

Proxy password

Enter the credentials for the proxy server and select to save. When the 2015 Creative Cloud applications are launched, and then query for a connection to the Internet, they recognize that the credentials have already been set and stored by the Creative Cloud Desktop application and leverages them.

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.

Muse
User is prompted multiple times to enter credentials. When user selects to save credentials dialog is suppressed and not prompt on any subsequent launches.

Authenticated proxy without CC Desktop app

If you have an authenticated proxy in your environment, but do not have the Creative Cloud Desktop app installed, then each individual application handles its own connection through the proxy with varying consequences. In most cases, a single prompt appears requesting proxy credentials. However, in some cases, multiple persistent dialogues appear at launch and when more functionality is accessed.

Proxy server credentials

To bypass authentication, some proxy servers allow for whitelisting of domains. A comprehensive list is available in the Creative Cloud enterprise endpoints document.

Behavior for environments that do not want services or are offline

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 and access services such as libraries that require the Creative Cloud Desktop app, then they are informed that they need to install.

There are many functions within the products themselves that lead to an Internet connection being requested some of these features are:

  • Sync Settings prompts and preferences
  • Sign In prompts and preferences (from Help menu and others)
  • Adobe Anywhere prompts in Premiere Pro/Prelude
  • Business Catalyst prefs in Muse
  • Lightroom Mobile prefs in Lightroom
  • Typekit prefs
  • CC Libraries and all other CreativeSync prefs

Sync settings

The Sync settings feature works in proxy environments when used in the latest versions of the following products:

  • Dreamweaver
  • Premier Pro
  • Media Encoder
  • Animate

See also

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy