|
|
Rank: Advanced Member
Groups: Member
Joined: 7/7/2014
Posts: 60
|
Hi,
The previous version of the EO web browser, as noted elsewhere, used the Adobe plug in to view PDFs. The 2015 version uses the built in PDF viewer, which apparently cannot open encrypted PDFs.
Is there a work around, am I missing something, or is this a real issue?
We have HIPAA info and don't want users to be able to save non-encrypted PDFs, so we always encrypt the PDF and then stream that for viewing and all that. We are wanting to upgrade to the latest version as we have some users with issues with Windows 10 and the older version.
thanks,
Craig
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
This would be a real issue. We are not aware of the fact that Chrome's built-in PDF plug-in can't load encrypted PDF. Can you send us a test file so that we can look into this? If that is indeed the case, I imagine we would have to add a flag to disable the built-in PDF plug-in.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/7/2014
Posts: 60
|
I've uploaded a file as below. This is a sample PDF encrypted as we do all our PDFs. Password for this one is asd123. As mentioned, previously the Adobe plugin would just ask for the password and open it. The current built-in viewer just indicates it can't open the file. This is streamed to the web browser as an application/pdf. Let me know if this is enough (and you can open it!) or if I need to write a sample test program. thanks! Link: Sample PDF
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, No. We can not open the file. Both IE and Chrome complains that Word Online can't open an encrypted PDF file. Can you email the file to us directly? See here for our email address: http://www.essentialobjects.com/Forum/Default.aspxThanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
This is just to let you know that we have tried this with the Adobe Plug-in but it still does not work. We did add a flag to disable Chrome's built-in PDF plug-in, but only to find out that Adobe PDF plugin does the same --- it won't open a file with password either. So you may want to adjust your design accordingly. One way to handle this (after we post the new build with the flag to turn off the built-in PDF plugin) is to handle the ShouldForceDownload event to force the WebView to treat PDF as a download, then launch the PDF Viewer on the end user's machine to view the PDF file after the download completes.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/7/2014
Posts: 60
|
Odd as that PDF does open for me via Adobe and via the older DLL via the Adobe plug in after prompting for a password. However - once there is a flag to use the plug ins we'll try again.
thanks,
Craig
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
We have posted a new build that added EO.WebBrowser.Runtime.DisableBuiltInPDFPlugIn property. You can try the new build and see if it resolves the issue for you.
In our next build EO.WebBrowser.Runtime.DisableBuiltInPDFPlugin will be renamed to DisableBuiltInPlugins since it effectives disable all plug-ins (even though for now that's only PDF).
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/7/2014
Posts: 60
|
Using 15.2.28.6 version (via Nuget) and it does not seem to make a difference. I've tried setting it in 2 places: in the App.xaml.cs where I set the license info, and in the actual Winform screen that uses the browser. And yes, this is primarily a WPF program but the EO browser is in a Winform - at one point the Winform DLL worked in ways that did not work in the WPF engine. Not sure if that should make any difference or not, but just in case...
I've set the options to both true & false just in case I had something backwards. I retested the prior build with the same file (we're actually using the .100 version as the .112 & .113 had some issues w/our web site) and the plug in works just fine.
Is this the current version referenced above or is there a delay in the Nuget release?
We have released the 2015.2.10.0 version for our Windows 10 users, but have tagged our release as a Beta as this is an issue. Fortunately there is a work-around as they can still download the encrypted PDF and print from that.
thanks,
Craig
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
This is consistent with what we see here ---- no matter which plug-in you use, you can not open an encrypted PDF file. The new flag allows you to completely disable PDF plugin so that the PDF request will be treated as download. So that might be the only option available for now.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/7/2014
Posts: 60
|
There seems to be a misunderstanding: the pre-2015 EO Browser, using the Adobe plug in, opens encrypted PDFs just fine - we've been doing that since we licensed the EO .Net Browser. So the program for Windows 7 & 8.1, using the .110 DLL, works as expected: when they 'print' an encounter, it streams the encrypted PDF to the EO browser, which, via the Adobe plug in, prompts for the password. Enter the password and the encrypted PDF opens in the EO browser. No problems, works great.
The 2015 browser really needs to allow the previous plug ins, if available, to work as they used to. While we don't let our users access the site directly, the developers do, and it behaves correctly: it streams the PDF and asks for the password, opening the PDF in the browser. We just can't do that in the Windows 10 version of the launcher (and we really hate having 2 versions of the Windows launcher as well)
While we do have a work-around, we and our clients would prefer the previous working behavior for the 2015 version and Windows 10.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Craig Oliver wrote:The 2015 browser really needs to allow the previous plug ins The new DisableBuiltInPDFPlugIn is exactly for this purpose. Once you set this property to true, it will load the Adobe Plugin (which comes when you install Adobe Reader), not Chrome's built-in PDF plugin. What we have observed is even Adobe's Plugin doesn't open encrypted PDF file from within Chrome. We do not know whether this is: A. Because Adobe changed something in their plugin, or B. Chrome changed something on their end, or C. It is that we broke something with the new release. It is unlikely that we broke something with the new release since plugin interface is pretty generic and if something about the interface is broken, then a lot of things would fall apart --- not just the PDF password part. Unfortunately this is the only case (case C) we will be able to fix since obviously if the change is on Adobe's side (case A), then there is nothing we can do, and even if the change is on Chrome's side (case B), we can not risk to undo something Chrome has done to roll it back to the behavior of an older version ---- it is simply not manageable for us that way. Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/7/2014
Posts: 60
|
Yay! As of 15.2.31.18, the disable built-in plug in appears to really disable the PDF plug in, and the Adobe one works - we can now open encrypted PDFs again.
thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
That's good news. Thanks for the update!
|
|