Adobe 22002486 Digital Signature User Guide - Page 71

Forcing a Certification Signature

Page 71 highlights

Acrobat 9 Family of Products Security Feature User Guide Controlling Signing with Seed Values Forcing a Certification Signature 71 3. Check Enable JavaScript. 4. Check Enable JavaScript debugger after Acrobat is restarted. 5. Restart Acrobat. To set seed values with the console (JavaScript debugger) in Acrobat, do the following: 1. Choose Ctrl + J. 2. Use the View drop-down list and select Console. 3. Enter the requisite JavaScript. 4. Highlight the JavaScript. If you do not highlight the JavaScript, only the last line of code is executed. 5. Press Control + Enter simultaneously or select the Enter key on the numeric keypad. Tip: When the JavaScript is executed correctly, the debugger returns "undefined." 6. Save the document, and test the field. Figure 55 Seed values: JavaScript debugger 5.2 Forcing a Certification Signature By default, signature fields can be signed with an approval or certification signature at the time of signing. However it is possible to constrain a signature field such that only a certification signature can used. Certification signatures are always associated with modification detection and prevention settings (and an mdp property) that control what types of changes can be made to a document before the signature becomes invalid. Changes are stored in the document as incremental saves beyond the original version of the document that was covered by the certifying signature. The mdp seed value allows you to control what behavior the signer can allow after signing (Figure 56).

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189

Acrobat 9 Family of Products
Controlling Signing with Seed Values
Security Feature User Guide
Forcing a Certification Signature
71
3.
Check
Enable JavaScript
.
4.
Check
Enable JavaScript debugger after Acrobat is restarted
.
5.
Restart Acrobat.
To set seed values with the console (JavaScript debugger) in Acrobat, do the following:
1.
Choose
Ctrl + J
.
2.
Use the
View
drop-down list and select Console.
3.
Enter the requisite JavaScript.
4.
Highlight the JavaScript. If you do not highlight the JavaScript, only the last line of code is executed.
5.
Press
Control + Enter
simultaneously or select the
Enter
key on the numeric keypad.
Tip:
When the JavaScript is executed correctly, the debugger returns “undefined.”
6.
Save the document, and test the field.
Figure 55
Seed values: JavaScript debugger
5.2
Forcing a Certification Signature
By default, signature fields can be signed with an approval or certification signature at the time of signing.
However it is possible to constrain a signature field such that only a certification signature can used.
Certification signatures are always associated with modification detection and prevention settings (and an
mdp
property) that control what types of changes can be made to a document before the signature
becomes invalid. Changes are stored in the document as incremental saves beyond the original version of
the document that was covered by the certifying signature. The
mdp
seed value allows you to control what
behavior the signer can allow after signing (
Figure 56
).