Macromedia live cycle 7.2 매뉴얼
Adobe LiveCycle
Before You Install
Installing and Configuring LiveCycle Security Products for JBoss
Preparing trust components for LiveCycle Reader Extensions 16
Extensions Server 6.1 or higher, your credential is still valid and, therefore, you do not receive a new one
from Adobe.
from Adobe.
If your organization purchases a production version of LiveCycle Reader Extensions, the production Rights
credential is delivered by Electronic Software Download (ESD), and you are notified by email. A production
Rights credential is unique to your organization and can enable the specific usage rights that you require.
credential is delivered by Electronic Software Download (ESD), and you are notified by email. A production
Rights credential is unique to your organization and can enable the specific usage rights that you require.
If you obtained LiveCycle Reader Extensions through a partner or software provider who has integrated
LiveCycle Reader Extensions into their software, the Rights credential is provided to you by that partner
who, in turn, receives this credential from Adobe.
LiveCycle Reader Extensions into their software, the Rights credential is provided to you by that partner
who, in turn, receives this credential from Adobe.
The Rights credential is used to extend the usage rights of each PDF file processed by
LiveCycle Reader Extensions. It is the most important part of the software licensing and should be stored
carefully in a secure environment.
LiveCycle Reader Extensions. It is the most important part of the software licensing and should be stored
carefully in a secure environment.
Preparing trust components for LiveCycle Reader Extensions
If you have not yet set up a trust directory to contain your LiveCycle Reader Extensions Rights credentials,
the installation program leads you through the process of setting up a trust directory and populates it with
the credential you will be using to apply usage rights to PDF documents. The installation program creates
a corresponding trust.xml file and places these components in the [product root]/trust directory.
the installation program leads you through the process of setting up a trust directory and populates it with
the credential you will be using to apply usage rights to PDF documents. The installation program creates
a corresponding trust.xml file and places these components in the [product root]/trust directory.
It also configures the credential that is deployed to the application server so that the deployed product
can access the credential information.
can access the credential information.
If your credential information changes, you must re-sign the trust.xml file, as well as reconfigure and
redeploy the credential. You can update the trust.xml file, re-sign the trust.xml file, and redeploy the
credential automatically using Configuration Manager. (See
redeploy the credential. You can update the trust.xml file, re-sign the trust.xml file, and redeploy the
credential automatically using Configuration Manager. (See
During LiveCycle Reader Extensions configuration, if you use an existing trust directory, the following
components are required.
components are required.
Trust component
Description
trust.xml
The trust.xml file contains mapping information for the certificates, credentials, and
CRLs used by the PDF Manipulation Module. This file references the contents of the
credentials, certificates, and CRL directories.
CRLs used by the PDF Manipulation Module. This file references the contents of the
credentials, certificates, and CRL directories.
LiveCycle Reader
Extensions Rights
credential
Extensions Rights
credential
A credential obtained from Adobe that enables you to apply Adobe Reader usage
rights to PDF documents. This credential is required for
LiveCycle Reader Extensions to run.
rights to PDF documents. This credential is required for
LiveCycle Reader Extensions to run.
keystore file
The keystore file stores private keys and their associated public key certificates. You
create the keystore, which is used for validating the trust.xml file against the
trust.sig file. It can be located anywhere on your system, but its properties are
configured and maintained within the Trust Manager Module.
create the keystore, which is used for validating the trust.xml file against the
trust.sig file. It can be located anywhere on your system, but its properties are
configured and maintained within the Trust Manager Module.
key pair
The private and public key generated and stored in the keystore is used for signing
and validating the trust.xml file. This key pair is separate from the credentials and
certificates described above. It is used to protect the integrity of the trust data and
is used only during the product startup to verify the data integrity.
and validating the trust.xml file. This key pair is separate from the credentials and
certificates described above. It is used to protect the integrity of the trust data and
is used only during the product startup to verify the data integrity.