Test assets before making them public

Secure Testing helps you define a secure test environment and build a robust B2B solution, based on a configurable set of IP address and ranges. This functionality lets you match your Adobe Dynamic Media Classic deployments with the architecture of your content management and business system.

With Secure Testing, you can preview the staging version of the website with unpublished content.

If desired, create a staging environment rather than making assets publicly available for the following reasons:

  • Preview websites before public launch (staging website).
  • Serve assets that require restricted access, such as eCatalogs that show prices in a B2B web application.
  • Use assets behind a firewall as part of product information management system, customer service application, training site, and so on.
NOTE

Secure Testing does not affect access to Adobe Dynamic Media Classic. Adobe Dynamic Media Classic security remains consistent and requires the usual credentials for access to Adobe Dynamic Media Classic and related web services.

How Secure Testing works

Most corporations run their Internet behind a firewall. Access to the Internet is possible through certain routes and typically through a limited range of public IP addresses.

From your corporate network, you can figure out your public IP address using websites like https://www.whatismyip.com or request this information from your corporate IT organization.

With the Secure Testing, Adobe Dynamic Media Classic establishes a dedicated Image Server for staging environments or internal applications. Any request to this server checks the origin IP address. If the incoming request is not within the approved list of IP addresses, a failure response is returned. The Adobe Dynamic Media Classic Company Administrator configures the approved list of IP addresses for their company’s Secure Testing environment.

Because the location of the original request must be confirmed, the traffic of the Secure Testing service is not routed through a content distribution network like public Dynamic Media Image Server traffic. Requests to the Secure Testing service have a slightly higher latency compared to the public Dynamic Media Image Servers.

Unpublished assets are immediately available from the Secure Testing services, without the need to publish. In this way, you can run a preview before assets are published to their public facing image server.

NOTE

Secure Testing services use the Catalog Server that is configured with an internal publish context. Therefore, if your company is configured to publish to Secure Testing, any uploaded assets in Adobe Dynamic Media Classic immediately become available on Secure Testing services. This functionality is true regardless of whether the assets are marked for publish on upload.

Secure Testing services currently support the following asset types and functionalities:

  • Images.
  • Vignettes (Render Server requests).
  • Render Server requests (supported, but must be requested explicitly by customer).
  • Sets, including image sets, eCatalog, render sets, and media sets.
  • Standard Adobe Dynamic Media Classic rich media viewers.
  • Adobe Dynamic Media Classic OnDemand JSP pages.
  • Static content, such as PDF files and progressively served videos.
  • HTTP video streaming.
  • Progressive video streaming.

The following asset types and functionalities are currently not supported:

  • Adobe Dynamic Media Classic Info or eCatalog search
  • RTMP video streaming
  • Web-to-print
  • UGC (User-Generated Content) services
IMPORTANT

Support for new or existing UGC vector image assets in Adobe Dynamic Media Classic ended on September 30, 2021.

Test the Secure Testing service

Test the Secure Testing service so you ensure that it works as expected.

  1. Contact Adobe Customer Care and request that they enable Secure Testing on your account.

  2. In Adobe Dynamic Media Classic, on the Global Navigation bar, go to Setup > Publish Setup > Image Server.

  3. On the Image Server Publish page, in the Publish Context drop-down list, select Test Image Serving.

  4. For the Client Address Filter, select Add.

  5. Select the check box so that the address is enabled (turned on), and then type an IP address and net mask in the respective text fields.

    NOTE

    If you add a single IP address and net mask, that address can make asset calls. However, any other IP addresses and net masks that you add are not permitted to make asset calls. As such, consider disabling (turn off) the check box in the step above to turn off the ability to specify an IP address and net mask. Doing so effectively permits all IP addresses to make asset calls, and they all show up.

  6. Do one of the following:

    • Repeat the previous two steps if you must add more IP addresses.
    • Continue to the next step.
  7. At the lower left of the Image Server Publish page, select Save

  8. Upload the desired images to your Adobe Dynamic Media Classic account.

    See Upload files.

  9. Make sure some of the images are marked for publish and others are unmarked, and then submit the publish job.

    See Publish files.

  10. Determine the name of your Secure Testing service by going to Setup > Application Setup > General Settings.

  11. On the Application General Settings page, under the Servers group, find the name to the right of Test Publish Context Server Name.

Contact Adobe Care if the server name is missing or the URLs to the server do not work.

Prepare website variations

You need two variations of a website that links the published and unpublished assets:

  • Public version - Link assets using your traditional Adobe Dynamic Media Classic URL syntax.
  • Staging version - Link assets using the same syntax but with the Secure Testing site name.

Run the tests

Perform the following tests:

  1. Check whether assets are visible from within your corporate network.

    From within the corporate network identified by the previously defined IP address range, the staging version of the website displays all images, whether marked for publish or not. As such, you can test without accidentally making images available before preview approval or product launch.

    Confirm that the public version of your site shows published assets as previously experienced with Adobe Dynamic Media Classic.

  2. From outside your corporate network, verify that nonpublished assets (that is, unmarked for publish) are protected from third-party access.

    Access your network from outside (such as, from your home computer or over a 3G connection), then verify that the public version of the site shows all published assets but none of the unpublished content.

    Confirm that the staging version does not show any asset because you are accessing the Secure Testing service from an unapproved IP address.

On this page