Adobe® LiveCycle® Digital Signatures was initially introduced under the name Adobe LiveCycle Document Security. With the release of LiveCycle ES in June 2007, this module was enhanced, reconfigured, and given a new name to more accurately reflect its capabilities within the overall suite: Adobe LiveCycle Digital Signatures ES. In October 2009, Adobe announced the LiveCycle LiveCycle Digital Signatures ES2 module, which enhanced its capabilities even further.
To learn more about the benefits of upgrading to LiveCycle Digital Signatures ES2, choose the tab that best represents your current software version.
Digital Signatures ES or Update 1
Upgrading to LiveCycle Digital Signatures ES2
- What are the new features in the LiveCycle Digital Signatures ES2 release?
- Digital Signatures ES2 includes the following new capabilities:
- Validation information is added post signing, which improves the regulatory compliance posture for common archiving requirements through more consistent and reliable signing.
- XFA form signature validation enables return trip validation of signatures to static and dynamic XFA forms.
- Accelerated Hardware Security Module (HSM) setup and usage improves assurance levels.
- How do I request an upgrade?
- If your organization holds a current maintenance and support contract, your designated point of contact receives an e-mail containing a complimentary upgrade coupon and detailed instructions on the process when each new version is released. If you don't have access to this e-mail or if you would like to learn more about the process, contact Adobe Customer Service.
Contact Adobe
Document Security 7.0
Upgrading to LiveCycle Digital Signatures ES2
- Why did Adobe change the name from LiveCycle Document Security to LiveCycle Digital Signatures?
- The new name, LiveCycle Digital Signatures ES2, more clearly reflects the digital signature functionality of this software. Adobe LiveCycle Digital Signatures ES2 lets you use digital signatures to preserve the integrity and authenticity of a document as it is transferred among users, whether it is passed within or beyond the firewall, downloaded offline, or submitted back to your organization. With LiveCycle Digital Signatures ES2, you can automate the process of certifying and signing documents, as well as validating signatures in documents that are submitted back to your organization. It also lets you automate the process of certifying and signing documents within corporate workflows.
- What are the top reasons to upgrade to LiveCycle Digital Signatures ES2?
- LiveCycle Digital Signatures ES2 offers many new features, including:
- Signing operation: Control several aspects of digital signatures used in a PDF document. The signing operation can define:
- How the digital signature appears in the document
- The signature algorithm used for signing
- The properties set in signature profiles used while signing
- The inclusion of embedded revocation checks in the signature field property
- Signature field creation: Control who can sign the PDF document using signature field properties defined in the PDF 1.7 specification.
- Signature field property modification: Control the signature properties of an existing signature field.
- Signature validation: Take advantage of the following features:
- Validation of XML digital signatures
- Configuration of revocation check failover from OCSP to CRL and CRL to OSCP
- Enhanced signature status information that can be used when developing business processes
- RFC3280-compliant validation and support for specifying path validation options at runtime
- Per-invocation control of the verification time and revocation check styles used for revocation checks, rather than using a global setting
- TrustStore configuration: LiveCycle Digital Signatures ES2 relies on the TrustStore repository as the database in which security data is stored. Trust chains are dynamically added to the TrustStore repository without requiring a restart of the database.
- Other API functionality: New APIs allow granular control over signature processing: ClearSignature, ClearSignatureField, and RemoveSignatureField. The signing profile can also be controlled using the API (seed values). You can also use the API to specify a policy OID for each trust anchor.
- Added standards compliancy: The following standards are supported:
- XML DigSig standards
- SHA-2 family of algorithms for encryption
- RFC3280
- Support for FIPS mode: Configure LiveCycle Digital Signatures ES2 to run with the Federal Information Processing Standards (FIPS) option enabled. The FIPS option restricts data protection to FIPS 140-2–approved algorithms using the RSA BSAFE Crypto-J 3.5.2 encryption module with FIPS 140-2 validation certificate 590.
- Configuration of service attributes in a web-based interface: Configure Signature service attributes in the Archive Administration area of the Adobe Administration Console. For example, set up watched folders and endpoints for service invocation, and configure remote APIs and parameters for orchestration.
- Signing operation: Control several aspects of digital signatures used in a PDF document. The signing operation can define:
