This article describes the various levels of support for proxy environments in Creative Cloud applications and services. If your enterprise environment is configured to use a proxy server with basic authentication, the following behavior is observed. Some proxy servers allow system admins to whitelist domains. If you are a system admin in your organization, use this document if you want to whitelist the appropriate domains.
You end users will, then, not be prompted to enter their proxy server credentials when they open any Creative Cloud application. When end users open a Creative Cloud application, they are prompted to enter their proxy credentials:. If you are a macOS user, you are prompted with the following dialog if you have not entered your proxy credentials in System Preferences :.
Enter your proxy credentials into your System Preferences on your computer and then click Try Again. When the Creative Cloud Desktop app is first launched and detects a proxy in place, it prompts for credentials. If you are already connected to the Internet, see the connectivity troubleshooting guide for more details. 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:. Legal Notices Online Privacy Policy. Proxy support in Creative Cloud products Search. User Guide. Legal Notices Online Privacy Policy. Buy now. Proxy support in Creative Cloud products Search. Proxy requirements for Creative Cloud Libraries.
Supported proxy setting types. 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 not supported for Creative Cloud products. Unsupported proxy setting types. Support for pac files.
NTLM authentication is not supported. In this use case, we have one or more machines that are being set up for use on an isolated network, but during the setup process they have access to the network. In this case, the procedure is as follows:. It does not require Internet access to any other host or service. If the server does not have consistent or any access to the licensing service, the proxy should be run in cache or store mode.
We recommend creating a dedicated user account to run the proxy service. Regardless of the port that will be used, the system must be configured to allow traffic from any host on the desired port e. Open a command-line terminal on the server and switch to the frl-proxy directory. Start the proxy with the start command. When you start the proxy for the first time, you will be prompted to specify a few configuration options.
These settings are saved to a configuration file. When the configuration file is present, the proxy will start without prompting for these options an additional time. Once the configuration wizard completes, configuration options are written to proxy-conf.
The configuration file can be edited in any text editor. You can also use the configure command to initiate a walkthrough of configuration options similar to the one presented on initial configuration. Proxy functionality is driven by command. The main command, start , is used to run the proxy according to the configuration file. Other commands exist to help configure the proxy or manage the cache. To get a full list of supported options and commands, pass the -h or --help option.
This not only documents supported commands, but shows which flags and options can be used with any command. The start command provides a limited number of command-line options to override certain configuration file options. These are specified after the start command. This allows customers the opportunity to examine the actual data transferred during the activation process and so ensure that no sensitive data is being exchanged.
SSL mode requires an X. The certificate file should be secured with limited file permissions so that only the account running the proxy can read it. If you store your password in the configuration, be sure to limit access to that file. The SSL certificate must be trusted by the client machines that contact the proxy, but it need not be a publicly-signed certificate that is, it can be a self-signed certificate that is installed on the client machines and marked as trusted.
SSL options are configured in proxy-conf. SSL mode can be toggled with the --ssl command-line option:. The mode can be set in proxy-conf. The clear command will clear the cache. No backup is made, so use this command with caution. Running clear by itself will prompt for confirmation:. The -y option can be used to bypass this confirmation, in case you need to clear the cache automatically without human interaction:.
A proxy running in cache or store mode can use the export command to export all unfulfilled license requests to a database file.
0コメント