FileOpen Client FAQ
Who is FileOpen Systems?
FileOpen Systems is a software development company based in Santa Cruz, California with remote offices around the globe. FileOpen Systems provides document security and rights management software to control access to documents, inside and outside of the corporate firewall. FileOpen software works with standard document formats and viewers such as Adobe Reader® and Microsoft Office® to manage access and enforce document use policy. With flexible solutions for both internal and cloud deployment, FileOpen document security products are trusted by corporations, governments, and publishers worldwide. For more information see the About FileOpen page.
What does a FileOpen Client do?
The first time, or in some cases every time a user attempts to access a FileOpen-protected document the FileOpen Client interacts with the document owner’s PermissionServer to authorize access and enforce the document owner’s acceptable use policy. The Client alone will not grant access to encrypted files; users must have the appropriate permissions from the document owner to access and use FileOpen-protected documents.
What does the FileOpen Client not do?
A FileOpen client alone will not grant access to encrypted files; users must obtain permission from the document owner. Please contact the document publisher/owner, not FileOpen Systems, for permission or any technical support required.
What, exactly, is a FileOpen Client?
FileOpen develops a set of clients/plug-ins to enable authorized access to FileOpen-protected PDF and Microsoft Office documents. These clients may differ slightly across platforms and operating systems. Details as follows:
The FileOpen Plug-in for Adobe Reader/Acrobat consists of the FileOpen.api Acrobat/Adobe Reader plug-in, and a number of ancillary modules required in order to operate from within the “protected mode” sandbox in Reader X and XI. These modules include the FileOpen Manager Service and the FileOpen Broker; details of the operation of these modules are available upon request to email@example.com.
Plug-in operating system compatibility includes Windows 7, 8, Vista, XP; Mac OSX, 10.5 or later; Linux Kernel 2.4 or later.
The FileOpen Plug-in for Foxit® Reader consists of the FileOpen.fpi plug-in, and an optional companion plug-in, fowpkbd.dll. The main plug-in, FileOpen.fpi, must be installed to open encrypted documents. The companion, fowpkbd.dll, 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.
Plug-in operating system compatibility includes Windows 7, 8, Vista, XP.
FileOpen also supports Bluebeam® Revu®, and Nuance PDF Converter. Within these environments the FileOpen Plug-in / Client is bundled into the application/viewer and require no additional installations.
Coming soon: Nitro Pro 8, Tracker PDFXChange.
The FileOpen Viewer for iPad and iPhone is a native iOS application that performs a client-server interaction with the document owner’s PermissionServer. The app supports both OPN (FileOpen’s native file format) and PDF files. For more details on the FileOpen Viewer App for iPad and iPhone, see our FAQ for Publishers or FAQ for End-Users.
Client compatibility includes iPhone (3GS, 4, 4S, 5), iPad, iPad Mini and iPod Touch (3rd Generation or later); running iOS 4.0 or later.
The FileOpen Client for Microsoft Office (beta) scontrols Office documents in the manner described in the Microsoft Office application programming interface (API) specification, via a set of Add-in Modules for Word, Excel and PowerPoint
Client operating system compatibility includes Windows 7, 8, Vista, XP. Office versions 2003, 2007 and 2010 are supported, with 2013 in development.
What is the current status of the FileOpen Plug-in for Adobe Reader/Acrobat on Linux?
The Linux Plugin for Adobe Reader /Acrobat is considered deprecated. Because of decisions made by Adobe the plug-in will load only in Reader 7 and 8 on Linux. Regrettably there is nothing that FileOpen can do to enable access to newer versions.
Where does the FileOpen Client get installed?
Depending on platform and operating system the Client is installed as follows:
Windows: FileOpen Plug-in for Adobe Reader/Acrobat
Adobe Acrobat/Reader loads plug-ins at application startup from:
Windows: FileOpen Plug-in for Foxit Reader
Foxit Reader loads plug-ins at application startup from:
C:\Program Files (x86)\Foxit Software\Foxit Reader\plugins
Windows: FileOpen Client for Microsoft Office
The FileOpen add-ins for MSOffice are loaded as COM .dlls and may be in any location, though are typically installed C:\Program Files (x86)\FileOpen
Macintosh: FileOpen Plug-in for Adobe Reader/Acrobat
On Macintosh the plug-in is sometimes difficult to find, as it becomes part of the "packaged" Acrobat/Reader application. The Plug-in can typically be found at /Library/Application Support/Adobe/Acrobat/
Linux: FileOpen Plug-in for Adobe Reader/Acrobat
Locations on Linux may be obtained by searching for "FileOpen".
How does the FileOpen Client get installed?
FileOpen Systems provides Client installers to our customers, who are free to distribute them to end users. FileOpen maintains a full listing of available Clients at http://plugin.fileopen.com/all.aspx.
Which privileges are required for the install?
In a Windows environment, users must have PowerUser (or Administrator) privileges to install plug-ins/clients.
Do you provide an installer for MSI?
msi installers are available from http://plugin.fileopen.com/all.aspx, along with instructions for signing that install for SMS delivery.
Once installed, what does the Client actually do?
When a user attempts to open a FileOpen-protected document, the Client reads information from the encrypted document and performs the following steps:
- Obtains information about the document being opened and the document owner’s authentication requirements, from the document. Depending on those document owner requirements, the Client then retrieves one or more of the following authentication tokens from the local machine/device context.
- A cookie from the User's login to the document owner’s server
- A username and password from a dialog presented to the User
- A MachineID and other identifying information from the local context
- Makes a request over http/https to the publisher's server, passing the document identifier, authentication token, and some data about the context in which the document is being opened.
- Retrieves a response from the publisher's server either granting or denying the user permission to open the document.
- Manages the use of that document according to the instructions given by the publisher's server.