View Only
  • 1.  Adobe Flash End of Life and impact on EngageOne 3.x

    Posted 10-09-2020 09:59
    Hi All,

    Recently it was informed by Pitney Bowes services team that the Adobe Flash player support will be ending on Dec 31, 2020. This means that EngageOne Administrator on versions before 4.4.10 will be impacted.

    We are using EngageOne 3.0.5 and 3.1.2 versions and we will be impacted with this EOL.

    Is there any other customer of EngageOne who will be impacted because of this? If yes, we would like to know your approaches to solve this issue.

    Thanks & Regards,

    ECM Team
    ABN AMRO Bank N.V.

  • 2.  RE: Adobe Flash End of Life and impact on EngageOne 3.x

    Posted 11-13-2020 14:29
    Hi, we have tested the following solution.
    Unfortunately it's client side, we have found nothing server side.

    As per my test, Flash plugin will stop working on 12th January 2021

    Adobe doc (chapter 5 - Administration - Enterprise Enablement) https://www.adobe.com/content/dam/acom/en/devnet/flashplayer/articles/flash_player_admin_guide/pdf/latest/flash_player_32_0_admin_guide.pdf

    These are the step for IE11 (you will find those for Chrome and other browser inside the document):

    1. Do not install the optional update KB4577586: https://www.catalog.update.microsoft.com/search.aspx?q=4577586
    2. When KB4577586 will be distributed by Microsoft, still do not install it. It will delete Flash for IE11 and will prevent it to be installed again
    3. Be sure to have the latest Flash version: http://www.catalog.update.microsoft.com/search.aspx?q=4580325 (for IE)
    4. Create the following files:
    5. Put these line of text in those files:
    6. This will allow Flash to run on the "AllowListUrlPattern"  website after EOL date
    7. If you use this procedure before EOL (now for example), all URL but those in the file will not work.

    You will find all the details in the documentation. As per my test now the procedure work.
    Can't say what will happen in 2021, and honestly it's not something I will rely on. Any update could change this behavior without notice, but at least it's documented by Adobe.

    If someone has found a "server side" solution, it would be really appreciated to share it.

    Diego Maggiori