FileOpen Systems is a software development company based in Santa Cruz, California. We are an Adobe Systems Security Partner. For more information see the About FileOpen page.
This plug-in is required to open PDF files encrypted by FileOpen rights management software, and is authorized by Adobe Systems to load in Adobe Acrobat and the free Adobe Reader. The plug-in manages the open and print commands in the Adobe Reader according to the access controls set by the publisher. Any access controls on the encrypted files have been placed there at the discretion of the document publisher. The plug-in alone will not grant access to encrypted files; you must follow the publishers' instructions for obtaining access.
The plug-in alone will not grant access to encrypted files; you must follow the publishers' instructions for obtaining access. Please contact the document publisher, not FileOpen Systems, for permission or any technical support required.
The plug-in package consists of the FileOpen.api Acrobat/Adobe Reader plug-in, and an optional companion plug-in, fowp4kbd.api. The main plug-in, FileOpen.api, must be installed to open encrypted documents. The companion, fowp4kbd.api, which restricts the taking of screenshots, is optional though some publishers may refuse to grant permission to open files if this plug-in is not installed.
In some instances, under Windows, the installer will also deposit a program in the system tray called FileOpen Certification Manager. This program manages the transition in and out of an Adobe viewer state called Certified Mode, and should only be installed on systems that have a copy of Acrobat/Reader 7 or lower and have installed at least one Adobe eBook; you can delete this program by clicking on its taskbar appearance and selecting Uninstall.
Adobe Acrobat loads plug-ins at application startup from a pre-defined directory, so the FileOpen.api plug-in has to be copied to that directory. By default, on Windows, the directory is:
On Macintosh the plug-in is difficult to find, as it becomes part of the "packaged" Acrobat/Reader application, but you can find a link to it by selecting the launch icon for the Adobe viewer and clicking Apple+I then finding the drop down for Plug-ins. From here you should FileOpen<ver>.acroplugin. You can also add/delete the plug-in from this menu.
Locations on Linux may be obtained by searching for "FileOpen".
FileOpen Systems provides installer programs that detect the location of the installed copy of Acrobat and copy the plug-in(s) to that location. We provide these installers to our customers, who are free to distribute them to end users. We also maintain https://plugin.fileopen.com/ - an installer on our website to which publishers may refer their users.
The installer on FileOpen's website attempts to provide a simple and seamless install via the browser. However, it works differently for different operating systems and browsers. The default automatic installer uses a Java "conveyor" to download and execute the installer. Users of IE without Java but with security settings that allow signed ActiveX controls to be loaded - the default setting - may see an ActiveX installer. The Java and ActiveX programs are only for convenience and the end result is the same regardless of whether the plug-in is installed via the web, by a downloaded copy of the installer, or manually.
Typically, Windows users must have PowerUser (or Administrator) privileges to run the installer, though all that is really required is write-permission to the Acrobat plug-ins folder.
The operation of the plug-in is identical whether it is placed into the Acrobat plug-ins folder location by the installer or via a manual operation. If you don't want to run the .exe or Java or ActiveX installer, you can get the plug-in from here and copy it to the location given above.
An .msi installer is available from here, along with instructions for signing that install for SMS delivery.
FileOpen.api is loaded by Acrobat or Adobe Reader at application startup, i.e. when you load Acrobat/Reader, it loads the plug-in. However, the plug-in is invoked only when a document calls for it (i.e. if you do not attempt to open any encrypted content, the FileOpen.api is inactive). In short, the plug-in does nothing unless a document encrypted by a publisher using the system is open.
When a user attempts to open a document encrypted by a publisher using FileOpen's software, the client reads information from the encrypted document and performs the following steps:
The FileOpen Client will work on Windows 98 or later, Macintosh OSX, iOS, Android and Linux.