You're viewing help content for version:
- 6.3
- Older Versions
The DocAssurance service requires RSA and BouncyCastle libraries. These libraries are installed along with the AEM Forms. Before configuring the DocAssurance service, Install and configure the AEM Forms package.
Note:
Before installing the AEM Forms add-on package, ensure that the installation path of the AEM Quickstart does not contain any spaces.
Out of the box, the DocAssurance service is not available for use. To use the DocAssurance service, bootdelegate the RSA and BouncyCastle libraries installed along with AEM Forms package. Perform the following steps to bootdelegate the libraries:
The DocAssurance service can apply usage rights to PDF documents. To apply usage rights to PDF documents, setup certificates for Reader Extensions. Perform the following steps to setup certificates:
-
Add the Key Store Password, Private Key Password, and Private Key Alias that is associated with the certificate to the respective fields. Click Submit.
Note:
To determine the Private Key Alias of a certificate, you can use the Java keytool command: keytool -list -v -keystore [keystore-file] -storetype pkcs12
Note:
In the Key Store Password and Private Key Password fields, specify the password provided with the certificate file.
Note:
On moving to production environment, replace your evaluation credentials with production credentials. Ensure that you delete your old Reader Extensions credentials, before updating an expired or evaluations credential.
To use AES 256 encryption for PDF files, obtain and install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files. Replace the local_policy.jar and US_export_policy.jar files in the jre/lib/security folder. For example, if you are using Sun JDK, copy the downloaded files to the [JAVA_HOME]/jre/lib/security folder.
The assembler service depends on the Reader Extensions service, Signature service, Forms service, and Output service. Perform the following steps to verify that the required services are up and running:
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.