Adobe 22002486 Digital Signature User Guide - Page 76

Specifying Timestamps for Signing

Page 76 highlights

Acrobat 9 Family of Products Security Feature User Guide Controlling Signing with Seed Values Specifying Timestamps for Signing 76 Table 9 Reason field behavior # of Reasons UI Pref Flag Reason Behavior 0 (empty array) on Required Reason field does not appear in UI. 0 (empty array) off Optional Reason field does not appear in UI. 0 (empty array) on Optional Display the default list. 1 or more off or on Required Display the custom reasons in a read-only field. 1 off Optional Reason field does not appear in UI. 2 or more on Optional Display the custom drop-down list and let the user enter a custom reason. 2 or more off Optional Reason field does not appear in UI. Example 5.4 Seed value: Custom signing reason // Obtain the signature field object: var f = this.getField("mySigFieldName"); f.signatureSetSeedValue( { reasons: ["This is a reason", "This is a better reason"], flags: 8 } ) Figure 59 Seed value: Reason not allowed error 5.6 Specifying Timestamps for Signing Timestamps originating from a timestamp authority's timestamp server are often associated with signatures. If it is critical in your workflow to acquire a secure timestamp with a digital signature, it can be controlled at the document level instead of relying on the signer's Acrobat configuration. Adding a seed value to the signature field with the timestamp server authority settings overrides the corresponding application level settings, if any. Use the timeStampspec specifier object's url and flags properties to specify a timestamp server. Table 10 Seed values: timeStampspec properties Property Type Description url string URL of the timeStamp server providing a RFC 3161-compliant timeStamp. flags number A flag controlling whether the time stamp is required (1) or not required (0). The default is 0. To specify a timestamp server: 1. Create a signature field with an intuitive name and tooltip.

  • 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
Specifying Timestamps for Signing
76
Example 5.4
Seed value: Custom signing reason
// Obtain the signature field object:
var f = this.getField("mySigFieldName");
f.signatureSetSeedValue(
{ reasons: ["This is a reason", "This is a better reason"],
flags: 8
} )
Figure 59
Seed value: Reason not allowed error
5.6
Specifying Timestamps for Signing
Timestamps originating from a timestamp authority’s timestamp server are often associated with
signatures. If it is critical in your workflow to acquire a secure timestamp with a digital signature,
it can be
controlled at the document level instead of relying on the signer's Acrobat configuration. Adding a seed
value to the signature field with the timestamp server authority settings overrides the corresponding
application level settings, if any. Use the
timeStampspec
specifier object’s
url
and
flags
properties to
specify a timestamp server.
Table 10
Seed values: timeStampspec properties
Property
Type
Description
url
string
URL of the timeStamp server providing a RFC 3161-compliant timeStamp.
flags
number
A flag controlling whether the time stamp is required (1) or not required (0). The default is 0.
To specify a timestamp server:
1.
Create a signature field with an intuitive name and tooltip.
0 (empty array)
on
Required
Reason field does not appear in UI.
0 (empty array)
off
Optional
Reason field does not appear in UI.
0 (empty array)
on
Optional
Display the default list.
1 or more
off or on
Required
Display the custom reasons in a read-only field.
1
off
Optional
Reason field does not appear in UI.
2 or more
on
Optional
Display the custom drop-down list and let the user enter a custom reason.
2 or more
off
Optional
Reason field does not appear in UI.
Table 9
Reason field behavior
# of Reasons
UI Pref
Flag
Reason Behavior