End of NPAPI, any impact for ENOVIA?

What is NPAPI?

Netscape Plugin Application Programming Interface (NPAPI) is an application programming interface (API) that allow plug-ins (more specifically, browser extensions) to be developed for web browsers. It was first developed for Netscape browsers, starting in 1995 with Netscape Navigator 2.0, but was subsequently adopted by other browsers.

The Final Countdown for NPAPI

In April 2015 NPAPI support will be disabled by default in Chrome and we will unpublish extensions requiring NPAPI plugins from the Chrome Web Store. Although plugin vendors are working hard to move to alternate technologies, a small number of users still rely on plugins that haven’t completed the transition yet. We will provide an override for advanced users (via chrome://flags/#enable-npapi) and enterprises (via Enterprise Policy) to temporarily re-enable NPAPI while they wait for mission-critical plugins to make the transition.
 In September 2015 we will remove the override and NPAPI support will be permanently removed from Chrome. Installed extensions that require NPAPI plugins will no longer be able to load those plugins.

NPAPI deprecation: developer guide

Yes, we do have a big issue here, but its for people who use Google Chrome, Opera etc. So you can clearly see the java applets thats been used in ENOVIA will be stopped eventually after this. So stick with IE browser that enables the applets to load and also advised by DS.

Leave a comment