Adobe Reader Mobile 10.1 for iOS and Android introduced support for accessing files secured by Adobe LiveCycle Rights Management. LiveCycle Rights Management protects sensitive documents by encrypting them with industry-standard AES encryption and enabling central management of their access permissions. Protections persist even when documents are accidentally distributed via email, the cloud, or saved on a lost mobile device.
Additional resources pertaining to Reader Mobile and LiveCycle include:
The following is required:
Reader Mobile 10.1 or later.
LiveCycle server versions:
- Adobe Digital Enterprise Platform Rights Management 10.x or
- Adobe LiveCycle Rights Management ES2 9.x with Service Pack 2 (version 18.104.22.168) patched with “QF 2.126” (available by contacting Adobe Support at http://www.adobe.com/support/livecycle)
The following is supported:
The following is not supported:
I am unable to open a protected document that I can open on my desktop. Why?
We have seen three typical reasons for this:
Why might there be a problem with SSL encrypting communications between Reader and the LiveCycle server?
Desktop OSes tend to be more forgiving of SSL trust issues. For example, despite being relatively unsafe, desktop applications allow trusting self-signed certificates. Reader Mobile, however, could refuse to open documents if the SSL certificate chains up to any self-signed certificates.
Desktop OSes also tend to have an additional root and intermediate CAs already deployed and either are more lenient of servers that do not contain all the intermediate CAs or that contain the chain in the wrong order. An administrator can determine whether all the intermediate certificates are sent in the correct order by running the following:
openssl s_client -showcerts -connect server.domain.com:443
If they are not sent in the correct order, recreate the application server keystore file by individually importing the appropriate certificates using the keytool application in the correct order. It may be helpful to try to browse to the server via an https connection in the device’s web browser. If an error may indicate a broader SSL configuration problem.
For additional guidance, contact Support at http://www.adobe.com/support/livecycle.
How will my experience differ from opening other PDFs within mobile Reader?
You will be prompted to identify yourself as the device communicates with the LiveCycle Rights Management Server.
If an author revokes a document or that document expires, can I view it with Reader Mobile?
Like on the desktop, you cannot open documents after they have been revoked or expired.
Why am I unable to open protected documents with dynamic watermarks?
The current version of Reader does not know how to display dynamic text or graphical watermarks. Because some customers believe the watermark is an important part of the document experience, and this version of Reader is not capable of displaying watermarks, when it senses that a protected document contains a watermark, it declines to decrypt. As a workaround, policy administrators can choose to change the policy to not take advantage of the dynamic watermarking feature. This behavior may change in the future. You can let us know if displaying dynamic watermarks is an important feature for you at http://www.adobe.com/support/livecycle.
Why am I unable to open a protected document when in “airplane mode”?
The current version of Reader does not support opening documents while offline.