Product Support Notice © 2018 Avaya Inc. All Rights Reserved. PSN # PSN005133u Original publication date: 24 Jan. 2018. This is Issue #01, published date: Severity/risk level Medium Urgency When convenient 24 Jan. 2018. Name of problem Ability to launch MPS applets such as MPS Manager with newer browsers. Products affected MPS 3.5 and MPS 4.1 Problem description Due to the removal of NPAPI from newer web browsers, the ability to launch MPS applets is impaired. This impacts the following features that are launched via a web session with the MPS AP. Feature Alternative MPS Manager View 4.1.0.7 or a newer MPS Manager patch uses a browser-independent Java Web Start technology for starting MPS Manager.
View 4.1.0.8 or a newer MPS Manager patch places the link to MPSManager.jnlp file on the MPSManager.html page. The user can follow the link to start MPS Manager by using Java Web Start if the browser does not support NPAPI plugins.
Mozilla Firefox 52 re-enables NPAPI plugin support when the user sets the plugin.load_flash_only variable to false.
Mozilla Firefox 52 Extended Support Release (32-bit) will continue offering support for NPAPI plugins until May 2018.
Some other web browsers still support launching Java applets, for example, Internet Explorer 11.
Resolution Apply one of the listed workarounds. Workaround or alternative remediation According to Firefox 52.0 release notes (https://www.mozilla.org/en-US/firefox/52.0/releasenotes), Mozilla removed support for Netscape Plugin API (NPAPI) plugins other than Flash. Other plugins like Silverlight, Java, and Acrobat are no longer supported.
An alternative way of launching MPS Manager Java applet using browser-independent Java Web Start technology was implemented in view4.1.0.7 patch. Customer must type the address of the MPSManager.jnlp file into the address bar of a web browser: http(s)://
However, the customers can still use the HTML page for launching MPS Manager applet via web browsers that still support NPAPI Java plugin: http(s)://
If the customer is using Firefox 52, there is a way to re-enable NPAPI plugins other than Flash (note that this workaround does not work with Firefox 53 and later releases):
Type about:config in the address bar, then right click, select New > Boolean, enter plugin.load_flash_only as the new Boolean value and set it to false. Once done, restart Firefox.
Another way to continue using NPAPI plugins in Firefox is to use Firefox ESR (Extended Support Release) instead. Note, that only Mozilla Firefox 52 ESR 32-bit release will continue offering support for the standards-based plugin support technology required for launching Java Applets (until May 2018). So download a 32-bit version of ESR from the official page: https://www.mozilla.org/en- US/firefox/organizations/all/ Install it to a folder other than the original Firefox installation folder if the customer is planning to use both versions on the same system, for example, to C:\Program Files (x86)\Mozilla Firefox ESR. Customers might also need to install the latest Java (jre, sdk). In this case, do not forget to add the address of the MPS Manager to the security exceptions via Java Control Panel and update system environment variables (like JAVA_HOME, JAVAHOME, JREHOME) with the new Java path prior to launching the Firefox ESR. Remarks n/a Patch Notes The information in this section concerns the patch, if any, recommended in the Resolution above. Backup before applying the patch n/a Download n/a Patch install instructions Service-interrupting? n/a No Verification n/a Failure n/a Patch uninstall instructions n/a Security Notes The information in this section concerns the security risk, if any, represented by the topic of this PSN. Security risks n/a Avaya Security Vulnerability Classification Not Susceptible Mitigation n/a
If you require further information or assistance please contact your Authorized Service Provider, or visit support.avaya.com. There you can access more product information, chat with an Agent, or open an online Service Request. Support is provided per your warranty or service contract terms unless otherwise specified in the Avaya support Terms of Use. Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED “AS IS”. AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS “AVAYA”), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS’ SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA. All trademarks identified by ® or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.