Adobe 22002486 Digital Signature User Guide - Page 77
Specifying Alternate Signature Handlers and Formats
View all Adobe 22002486 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 77 highlights
Acrobat 9 Family of Products Security Feature User Guide Controlling Signing with Seed Values Specifying Alternate Signature Handlers and Formats 77 2. Create the JavaScript that gets the field object and uses the seed value method (Example 5.5). 3. Provide a URL for the timeStampspec object. Tip: Timestamp seed value settings override the end users' application settings, if any. 4. Enter a flag value to indicate whether the value is required or not. If it is required, the field is automatically timestamped on signing. If the application cannot find the server, an error appears (Figure 60). If it is not required, the field will is automatically timestamped on signing if the application can find the server. If it cannot find the server, the signature is not timestamped and no error appears. 5. Run the JavaScript, save the document, and test the field. Example 5.5 Timestamp server seed value // Obtain the signature field object: var f = this.getField("mySigFieldName"); f.signatureSetSeedValue( { timeStampspec: { url: "http://153.32.69.130/tsa", flags: 1 } } ) Figure 60 Time stamp server error 5.7 Specifying Alternate Signature Handlers and Formats Organizations may choose to use alternate signature technologies or implementations (signature handlers), provided by third party software developers. For example, a corporation may have deployed Entrust Entelligence® to all their desktops and may choose to use the Entrust signature plug-in with Acrobat. Two seed values allow authors to specify which signature handler and format to use. By using a standard format, interoperability across multiple signature handlers is possible. Filter also allows authors to control what handler version is required. For example, for Acrobat 6.x, the PPKLite version is 0. For Acrobat 7.x, the PPKLite version is 1. Therefore, specifying a version of 1 prevents signers from signing when their application is older than Acrobat 7.0. Custom handlers can use any version as required.