Additionally end-users will not be able to use any other Pulse Secure's Java Applet based features such as JSAM, Premier Java RDP (HOB), etc from Google Chrome browsers. Once NPAPI plugins are disabled, end-users will not be able to install or launch Pulse Secure components from a Chrome browser using Pulse Secure's Java Setup Applet. ![]() ![]() What is the impact of this on Pulse Secure Products? Since Sept 2015 (Chrome v.45) Google Chrome has deprecated the support for NPAPI based plugins including Java plugin, for more details refer to this Chrome link To launch Java Applets from browsers they rely on a Java Plugin (the Java Plugin is a NPAPI based plugin) The Java applet is also used to communicate between the browser and the installed client components. When logging in from a Google Chrome browser, Pulse Secure products use a Java applet (called the Setup Applet) to install client components such as the Pulse Secure Desktop Client, Network Connect, Windows Terminal Services, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |