Java plug-in no longer in Safari 12.0
After seeing an update for Safari today, I noted that it contained security updates, so I upgraded. After upgrading, however, I could no longer launch a Java applet for remote desktop access that I’ve used for years. The upgrade put Safari at version 12.0 (13606.2.11). There no longer is a Java plug-in under the list of available plug-ins that can be enabled/disabled for individual web sites. Specifically, it used to look like this:
Now I now longer see Java in the list of plug-ins at the lower left. I re-installed JRE 8 Update 181 from Oracle to no avail. How are we supposed to run Java applets/applications from Safari in version 12.0 and later? My MacOS is Version 10.13.6 (17G65).
MacBook Air, macOS High Sierra (10.13.6)
Posted on Sep 17, 2018 1:34 PM
After reading more (see How to Use Java, Silverlight, and Other Plugins in Modern Browsers and https://jaxenter.com/clock-ticking-java-browser-plugin-will-deprecated-soon-1315 46.html), Safari has been one of the longest browsers to support the NPAPI Java plug-in. That support seems to have ended with Safari 11. There are some alternatives according to the jaxenter.com article, but they require modifying the Java application.
Posted on Sep 18, 2018 8:57 AM
Similar questions
java plugin Hi all,As Safari 12 no longer supports Java plugin, are you aware of any alternative solution to use it?I use Java to remotely to connect to my work PC, this Safari update doesn’t make the life easier.
Make Safari default browser Unable to make Safari my default browser after issues with one web site forced a change. Running Monterey 12.6 and Safari 16.0. Old Apple Support does NOT work on M1 iMac.
Safari not compatible with current version of Big Sur 11.1 Hi I was part of the appleseed program and had Big Sur 11.2 on my Mac mini until today. I reverted back to the latest public release version 11.1 because 11.2 was causing some issues. My issue is that when reloading version 11.1 to revert back, it DID NOT reload Safari and I’ve tried it multiple times now. As a result I cannot use Safari as it tells me that the version of Safari I have requires Big Sur 11.2 and thus will not open because I have Big Sur 11.1. I’m stuck. Any help is appreciated.
I hope this is not too late, but I too depend on a Java plugin to connect to work. I found in another article that using «SeaMonkey» from the Mozilla group did the trick! https://www.seamonkey-project.org
It includes an email, newsgroup, and feed client too but I only use it as a browser for my Java-Plugin required applications. Now I am back online and saving Safari and all those other browsers I tried (with no avail) for other uses.
Hope it works for you — I am recommending it to all my cohorts who telecommute with Macs to try it out.
When I try to launch the Java application, I get the following image that says «Unsupported Plug-in» in a Safari window:
I have the very same issue. I have many work needs that require Java and will go back to last version of Safari if 12.0 doesn’t provide a plug in any longer.
Any help, please?! Thanks.
I am having the same issue — in my case my Java app works but there I need to enable the «Unsafe» mode for the Java App and that has also disappeared.
I am assuming there is a workaround or the feature is hidden somewhere else. waiting. 😕
Plugins are no longer supported in Safari 12.
I don’t think that’s correct. I still see other plug-ins for Adobe Flash, Google Talk, etc. The screenshot below is from my newly installed Safari 12.0
What’s the basis for your assertion that plug-ins are no longer supported?
Some plugins are supported.
See the last item in the screen shot.
After reading more (see How to Use Java, Silverlight, and Other Plugins in Modern Browsers and https://jaxenter.com/clock-ticking-java-browser-plugin-will-deprecated-soon-1315 46.html), Safari has been one of the longest browsers to support the NPAPI Java plug-in. That support seems to have ended with Safari 11. There are some alternatives according to the jaxenter.com article, but they require modifying the Java application.
I’m having the same problem with 5 different Macs within the family (iMac, 2 new MacBook Pros, 1 old MacBook Pro, and 1 old MacBook Air). The use a program that requires Java plugin support and now I can’t use it after the upgrade to Safari 12.0. I tried everything and was finally able to wipe an old 2013 MacBook my kid used before she got her new Mac this year. It came back with Safari 10.12 after the install which allowed me to use the Java plugin. Unfortunately, I can’t do that easily for the rest of my computers because the shipload of software and documents. Now the only device I can run Java on is old and heavy MacBook. I used the new MacBook or MacBook Air when I travel but now I can’t do that. I have to carry that old computer just to use 1 program?
Apple has been controlling and now they are getting more and more controlling. If Java is NOT safe then a user should be able to use it on their own risk. All Apple has to do is give the warning!
Why is Java plug in being deprecated
As per the Java 9 specifications, Java plug in is being deprecated. A well known reason behind this is the removal of plug in support entirely by the popular web browsers. Is there any other reason why this step is being taken? I had read in one of the articles (from unreliable source) that the plug in mechanism lead to security risks. Is that true? If yes how? Also, why did each of the popular browsers took decision on removing support for the plug in?
@litelite: Thanks for the quick response. That partly answers my query. However, I’m unable to understand how is security compromised by the plug-ins.
@litelite Can you transform that to an answer? It likely answers OPs questions, as he already mentioned.
1 Answer 1
The browsers removed it for the same reasons they removed flash. It relied on a third party plugin that was filled with security holes that they could not patch themselves. And they have that new shinny technology (HTML5 and all the goodies that came with it) that meant they did not need to tolerate it anymore because all the things the plugin made possible are now available without. And now that no one is really using it, it’s not worth maintaining.
And the reason for all the security holes is because the plugin had a lot of bugs that could be exploited by an attacker to gain access to the client’s machine.
Related
Hot Network Questions
Subscribe to RSS
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.7.27.43548
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
Why were applets deprecated in JDK 9?
I have recently read in an article posted by Oracle that they are going to mark the Applet class as deprecated in JDK 9. I have little experience with applets; I have only written some to understand the basics. Why are they unpopular, and what is the main reason for their deprecation?
2 Answers 2
Applets were very popular a couple of years ago, but now the browser world changed and security is becoming a major focus for all major browser vendors.
The Java team gave its complete set or reasons, alternatives etc. in the document Migrating from Java Applets to plugin-free Java technologies. On page 4, there is the following Executive Overview:
With modern browser vendors working to restrict or reduce the support of plugins like Flash, Silverlight and Java in their products, developers of applications that rely on the Java browser plugin need to consider alternative options. Java developers currently relying on browser plugins should consider migrating from Java Applets to the plugin-free Java Web Start technology.
Supporting Java in browsers is only possible for as long as browser vendors are committed to supporting standards based plugins. By late 2015, many browser vendors had either removed or announced timelines for the removal of standards based plugin support, while some are introducing proprietary browser-specific extension APIs. Consequently, Oracle is planning to deprecate the Java browser plugin in JDK 9.
The deprecated plugin technology will be completely removed from the Oracle Java Development Kit (JDK) and Java Runtime Environment (JRE) in a future Java release TBD. Java Web Start applications do not rely on a browser plugin and will not be affected by these changes.
Oracle’s finally killing its terrible Java browser plugin
By Tom Warren , a senior editor covering Microsoft, PC gaming, console, and tech. He founded WinRumors, a site dedicated to Microsoft news, before joining The Verge in 2012.
Share this story
Oracle is taking the final step to rid the web of its terrible Java browser plugin. While the plugin started off life back in the ’90s as an innocent way to bring app-like features to browsers, in recent years it has been a headache to users and IT admins struggling to fight against its mountain of security flaws and malware issues. Microsoft and Google have both killed off support for Java applets in Edge and Chrome, leaving Internet Explorer and Safari as the only alternatives for people who really need Java applications in their browser.
Modern browsers don’t care about Java anymore
Google removed the technology needed for Java applets in September, and Microsoft’s latest Windows 10 operating system shipped with its Edge browser six months ago without support for plugins like Java. Mozilla has announced plans to remove support for plugins like Silverlight and Java in Firefox by the end of the year. Oracle is now planning to deprecate the Java browser plugin in its JDK 9 release due in September.
It’s hard to say exactly when Java browser plugins will fully disappear, but if you’re using a modern web browser like Microsoft Edge or Google Chrome then you’re already one step ahead. Businesses who still rely on Java browser plugins will be able to continue using them in compatible browsers for the short-term, but Oracle is providing them with a big warning that this is the final nail in the coffin of its Java browser plugin.