Some Password Protected documents can not be unlocked with Embed API

[Gardiant265466655uq0]

Issue in /src/pages/overview/pdf-embed-api/index.md

The Embed API seems no longer be able to open a password protected document IF the document was protected by Microsoft Word. However, it can open a password-protected document if the password was added using the Adobe Password Protect Tool. The password for these sample documents is "pass123".

The Chrome, Firefox and even Edge can open the same document, regardless of what we use to protect the document.

It does prompt to enter the password but upon entering the password, it logs the following error in the browser console:

std::invalid_argument at ___cxa_throw (https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.js:1:28684) at self.___cxa_throw (https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.js:1:206) at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at invoke_viii (https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.js:1:103321) at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-funct... at ccall (https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.js:1:79063) at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.js:1:79368 at be (https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/acrobatProxy.js:2:79868) at Ae (https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/acrobatProxy.js:2:83764) at we (https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/acrobatProxy.js:2:85868) at Se (https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/acrobatProxy.js:2:85552) at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/acrobatProxy.js:2:85830

[Raymond Camden]

Why not add the password after Word converts to PDF? At the end of the day, I think thats probably a fair expectation - if it's not *directly* protected via Acrobat, or the online tool you shared, than support may not be gauranteed. Is adding the password _after_ the conversion something that would work for you?

[Raymond Camden]

As a followup, if you open the PDF in Acrobat, does the password work?

[Raymond Camden]

Ok, I tested your output, and it _does_ work in Acrobat. I'll file a bug report.

[Raymond Camden]

After filing this internally, engineering came back with some interesting findings. 

1) For them, if they use the Word password protect open feature, and then they export to PDF, they get a warning that the password will NOT be in the PDF. I did not get a warning in my test, but I can verify that the exported PDF does not have a password.

2) If they used export via Create PDF/XPS and in options there, used a password, they were able to see the same issue you have here.

Can you let me know if you have an enterprise account w/ Adobe?

[Gardiant265466655uq0]

1) We tried adding password to the Word file and then saving it as PDF, we got the following warning and clicking on Yes, the PDF did not have the password. The password was applied only to the Word file. Same behavior as your engineering team.

2) Yes, I guess this is the way most people would create password protected PDFs from Microsoft Word so essential to make this flow work.

We do not have a paid enterprise account with Adobe, just a free account with 

Acrobat Services: PDF Services API.