Credentials Element - Adobe LIVE CYCLE 7.2 - INSTALLING AND CONFIGURING Manual

Security products for jboss
Hide thumbs Also See for LIVE CYCLE 7.2 - INSTALLING AND CONFIGURING:
Table of Contents

Advertisement

Adobe LiveCycle
Installing and Configuring LiveCycle Security Products for JBoss

credentials element

The
credentials
p12record
hsmrecord
MSCAPIrecord
Passwords required to access the private keys are supplied through the API and are not included in the
trust.xml file. The PDF Manipulation Module searches the credentials directory for file names. The
credentials directory is imported into the deployment unit.
The available record types and corresponding attributes are described in this table.
Record type
p12record
hsmrecord
MSCAPIrecord
element has three sub-elements that describe a type of private key container:
—A reference to a PKCS#12 (.p12) file stored on disk.
—A reference to an HSM.
—A reference to an entry in the Microsoft database (on systems that run Windows).
Attributes
alias
p12file
sha1
alias
dllpath
slot
sha1
alias
sha1
Description
The name by which the credential is known to the PDF
Manipulation Module API. It must be unique in the credentials
section of the trust.xml file.
The PKCS#12 file name. It is searched for among the files
imported into the deployment unit.
(Optional) The SHA1 fingerprint of the corresponding
certificate. The
value can be used to distinguish among
sha1
different keys if more than one is stored in a single PKCS#12
file. If the
value is not provided and the PKCS#12 file
sha1
contains multiple appropriate credentials, an exception is
raised.
The name by which the credential is known to the PDF
Manipulation Module API. It must be unique in the credentials
section of trust.xml.
The location of the DLL in the file system. For HSM support, a
DLL is required that implements the PKCS#11 interface for that
particular HSM.
The slot number that identifies where the private key is stored
on the HSM.
(Optional) The SHA1 fingerprint of the corresponding
certificate. The
value can be used to distinguish among
sha1
different keys if more than one is stored in a single PKCS#12
file. If the sha1 value is not provided and the PKCS#12 file
contains multiple appropriate credentials, an exception is
raised.
The name by which the credential is known to the PDF
Manipulation Module API. It must be unique in the credentials
section of the trust.xml file.
The SHA1 fingerprint of the corresponding certificate. This
value must be used to select among the different credentials
stored in the Microsoft certificate store.
Content and Format of the trust.xml File
credentials element
81

Advertisement

Table of Contents
loading

This manual is also suitable for:

Livecycle 7.2

Table of Contents