This quick user guide is intended for ADC users in the context of Adobe Flash EOL and applies to ADC version 1.4 or higher.

Please check the complete User Guide for more details and recommendations for administrators (e.g. to deploy ADC to the end user in a secure way for your enterprise).

1. Download and install/unzip the latest version of Axway Desktop Client.
   • The tool is delivered as a ZIP file that needs to be unzipped in a local directory on your workstation (not a shared drive) with proper rights to execute a program downloaded from the internet.
   
   
   
2. Locate and secure the pepflashplayer.dll (64 bit version) available on your Windows environment.
   Axway Desktop Client needs a specific flash player DLL called Pepper to render the flash application. Due to legal restrictions from Adobe, Axway cannot embed this flash player DLL in Axway Desktop Client.
   Therefore as a pre-requisite for the use of the Axway Desktop Client, the client will require the specific flash player DLL be sourced for use.
   For enterprise distribution and certificate management recommendations please refer to our Axway Desktop Client Documentation.
   
   Examples of where this file can be found with a typical Flash Player installation:
   • If you downloaded and installed Flash player from https://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player_ppapi.exe (Offline installer - recommended)
     or
     https://get.adobe.com/flashplayer/ (Online installer) - no longer available
     then the path to the pepflashplayer.dll is:

   c:\Windows\System32\Macromed\Flash\pepflashplayer64_32_0_0_465.dll
       

   • If you are using Chrome for accessing Flash pages then you may find the pepflashplayer.dll in the following path:

   c:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\PepperFlash\32.0.0.465\pepflashplayer.dll
       

   
   ⚠Important: The Adobe Flash installers above will not be available anymore after December 2020 while the Online installer itself will not work anymore (as it will try to download content that will not be available).
   Also, some existing Flash DLLs may be removed by future updates at OS or browser level or by automated uninstall requests.
   pepflashplayer.dll is a prerequisite for running ADC and it is critical to secure future access to this DLL by making a backup copy so the DLL can be retrieved in case it is accidently removed.
   After locating the DLL, we recommend you to copy it in a secure directory of your choice that you will then reference in Axway Desktop Client configuration (“pluginLocation” described in the next step).
   
   More details regarding identifying the correct pepflashplayer.dll can be found in KB 181379 FLASH EOL: Identifying and using the correct pepflashplayer.dll
   
   
3. Edit the whitelist.json from axway-desktop-client-1.4.0\resources\whitelist.json path and review, adjust the following parameters:
   
   The whitelist.json is a JSON file which lists all the websites allowed by Axway Desktop Client. The user is only allowed to connect to a website from this list and any redirection to websites outside the list are blocked by the tool.
   • BlockUntrustWebsite: Default (and recommended) value: “Yes”. Can be set to “No” in order to test HTTP URLs or URLs that are not presenting a valid/trusted certificate. The value in the example below is set to “No” for testing reasons only.
   • pluginLocation: path towards the location identified at point 2.
     ⚠ Important: We recommend to not point directly to the pepflashplayer.dll located in a Chrome or Windows installation directories as future system or browser updates may suppress or automatically update the DLL and impact the behavior of ADC.
   • title and url: name and URL of the Flash page that you wish to test.
   Please refer to the complete User Guide for recommendations and extra details on all parameters
   
   
   whitelist.json example:
   

   {
     "BlockUntrustWebsite": "No",
     "logFolderLocation": "C:\\log_folder\\",
     "cleanCookies": false,
     "pluginLocation": " C:\\secured_location\\pepflashplayer.dll ",
     "urlOptions": [
       {
           "title": "PassPort HTTP access",
           "url": "http://passport.axway.com:6901/"
       },
       {
           "title": "Passport HTTPs access",
           "url": "https://passport.axway.com:6453/"
       },
       {
           "title": "Passport SSO access",
           "url": "https://passport.axway.com:6900/"
       },
       {
           "title": "CentralGovernance HTTPs access",
           "url": "https://cg.axway.com:6900/"
       },
       { 
           "title": "Omnivision Investigation Portal",
           "url": "http://<ip>/DisplayPortal.html"
    },
       { 
           "title": "Omnivision Investigation",
           "url": "http://<ip>/"
    },
       { 
           "title": "socket for OMVi", 
           "url" : "xmlsocket://<ip>:4428/" 
    },
       { 
           "title": "Development Track & Trace", 
           "url" : "https://dev.tnt.axway.com/trackntraceserver/" 
       }
     ]
   }
           

   
   
   
4. Test Axway Desktop Client by running axway-desktop-client.exe.
   1. Execute axway-desktop-client.exe from the installation directory
   2. Select the desired website from the drop-down menu
   3. Click the "Connect" button
   
   
   
   
   If you see message saying that the website is not trusted (in case of HTTPS URLs, for example), it’s due to the fact that certificates aren’t managed correctly, please refer to the complete User Guide for more information.
   
   
5. Test Axway Desktop Client from a desktop with the date set in the future: after January 12^th 2021.
   This step is optional but recommended in order to verify that the configuration is correct:
   1. Close Axway Desktop Client and other browsers that you wish to test.
   2. Change the date on your local workstation to a date after January 12th 2021.
   3. Try accessing the application with your usual browser: => Flash will not run, the application cannot be accessed.
   4. Try accessing the application with Axway Desktop Client: => Flash should run, the application should display correctly. Few examples below:
      
      
      

FLASH EOL related articles:

FLASH EOL: Axway products impacted by Adobe Flash Player end of life

FLASH EOL: Axway Desktop Client - simplified User Guide

FLASH EOL: How to override FLASH EOL and whitelist domains in main browsers on Windows

FLASH EOL: How to activate debug when troubleshooting Axway Desktop Client?

FLASH EOL: Identifying and using the correct pepflashplayer.dll