CCC5.7 Creating a proxy site (optional)

Version 5.7 is the last version supporting a proxy site. Proxy sites will no longer work with versions 5.8+.

Background information

The connector can use the Media Manager's Config Manager opposed to earlier versions of the software, where the Creative Cloud Connector always had its own version in the Config Manager. This update means that creating a proxy site is no longer required, but can still be performed, if separate configuration is needed.

When opening the plugin for the first time changing the environment, there appears a prompt to enter an url. Dependent on whether the proxy site was created, there are two ways the user can point the CCC to a Config Manager version:

Use the MM5's Config Manager version by providing the MM5's url
Use a CCC-only Config Manager version, by proving the url for the proxy website.

Installation of a proxy website

Step 1: Preparation

To install a proxy website please perform the following steps:

Copy the provided zip file "digizuite-adobe-connector-website.5.x.x-xxxx.zip" onto your server and unzip it into a new folder.
Copy the unzipped folder into the "Webs" folder (usually located on C:\webs)
Rename the folder URL you wish for your CCC to be accessible through.

Step 2: Creating a Config Manager version solely for CCC to use

This step is the core of this guide. Here you create what the the CCC points to. In other words, the other steps are there to allow the CCC plugin to point to the Config Manager version you create here.

To start, go to you DAM Center, and navigate to System tools → ConfigManager → Media Manager 5 → 5.x.x.

In here, you have the ability to create CCC's Config Manager version.

Press the text field in the top-right corner, and input a name of your choosing, for example ‘CCC’ or ‘Default’.

Please note that the name itself is not important, but it cannot be changed nor deleted later on.

After creation, the new Config Manager version can be found beneath System tools → ConfigManager → Media Manager 5 → 5.x.x.

In here - locate the ID of the Config Manager version by pressing the Menu button → Version information (found next to the Create new version button):

You'll be seeing something akin to the following image:

Note down the Version id - in this case, it's "/1/1/". This will be used in the following step.

Step 3: CCC website configuration

The proxy website needs to point to the new version you created. Additionally, it requires some info to be set, in order to fully function.

Navigate to the CCC website files from step 1 (again, usually found in C:/webs), and open the file named appsettings.json. We recommend Notepad++ for editing such files:

{
  "Logging": {
    "LogLevel": {
      "Default": "Warning"
    }
  },
  "AllowedHosts": "*",
  "EnablePrerendering": false,
  "ForceHttps": true,
  "HttpsPort": 443,
  "MediaManagerConfiguration": {
    "GuestUsername": "Guest",
    "GuestPassword": "0ea2f02d5f73c86c220ff08b23d1c3f1",
    "ApiDomain": "",
    "UseHttps": true,
    "WowzaServer": "",
    "WowzaAppName": "mmapp",
    "AbrMediaId": "666",
    "EnabledFeatures": [],
    "InstrumentationKey": "#{instrumentationKey}",
    "ProductVersion": "#{productVersion}",
    "VersionId": "!/5/",
    "UseFederatedAuthentication": false,
    "EnableNormalLogin": false,
    "BusinessWorkflowServiceUrl": "http://localhost:60000/"
  }
}

The easiest way to configure this is to look at your Media Manager website's appsettings.json file, and copy its values.

Here's a rundown of what the fields are used for:

Placeholder	Description

Placeholder	Description
ApiDomain	Insert the DAM Center's url. This is used to redirect the calls to the proxy site onto the corresponding DAM Center.
VersionId	Input the CCC's Config Manager Version ID, which we located in the last step. (e.g. "/1/1/") Due to legacy code, please insert a "!" in front of the version. Thus making it say e.g. "!/1/1/"
UseFederatedAuthentication	Must be set to "true" if using SSO.
EnableNormalLogin	Must be set to "true" if normal login should be enabled together with SSO.

Please note: The fields "WowzaServer", "EnabledFeatures" and "InstrumentationKey" are not relevant for the CCC and can be disregarded.

Step 4: Creation of a New IIS Website

Open the IIS

Unfold the menu under the server name and right-click the web server and select "Add website...".

A new prompt will appear.

Input the following:

Site name: Input the URL
Physical path: Input the path to the folder in webs. Either click "..." or simply paste in the path yourself.
Host name: Input the URL
Type: Change type to "https".
Require Server Name Indication: Check off the box
SSL certificate: Select a SSL certificate that is usable for the URL you've chosen.
Click "OK".

(Optional): Go into the site's bindings and add a "http" binding:

Step 5: Ensure that PortalName is set to be the MM5 site's URL

Define PortalName which could be found withing appsettings.json "ProductConfiguration" section to be either:

The MM’s URL if the MM does not have this defined
The same as the MM’s if the MM has it defined

Example of relevant json files:

D:\webs\test-ccc.qa.digizuite.com\appsettings.json

D:\webs\test-mm5.qa.digizuite.com\appsettings.json

The required value for Portalname could be found within table:

SELECT TOP (1000) [ProductName]
      ,[PortalName]
      ,[MemberId]
      ,[Configuration]
  FROM [test_dam].[dbo].[LoginService_Preferences]