Adobe 22002486 Digital Signature User Guide - Page 100

Validating Signatures

Page 100 highlights

7 Validating Signatures When you receive a signed document, you may want to validate its signature(s) in order to verify who the signer was, when they signed it, and what was actually signed. Depending on how you have configured your application, validation may occur automatically. However, understanding both how to validate a signature manually as well as what signature components are analyzed during the validation process can facilitate trouble-free workflows and mitigate signature status problems. Participants in signing workflows may also want to configure their environment to streamline the validation process and control what kinds of content in signed documents can be run on their machine. The following sections provide validation details:  "Signature Validity Basics" on page 100  "Setting up Your Environment for Signature Validation" on page 102  "Validating Signatures Manually" on page 106  "Troubleshooting a Signature or Document Status" on page 115  "LiveCycle Dynamic Forms and the Warning Triangle" on page 121  "Save as 8.1 except that changes to document behavior are detected and invalidate an approval signature: prior versions displayed a yellow triangle upon discovery of changes to document behaviour." on page 121  "Viewing and Comparing Changes and Versions" on page 122 7.1 Signature Validity Basics As part of the signature validation process, Acrobat and Adobe Reader verify the signer's identity as well as the document's integrity. 7.1.1 What Makes a Signature Valid? Signature validity is determined by checking the signature's digital ID certificate status (is it valid and trusted?) and document integrity (has it changed since being signed?):  Authenticity verification confirms that the signer's certificate or that one of its parent certificates exists in the validator's list of trusted identities and that the signing certificate is valid at that point in time according to the user's Acrobat or Reader configuration (time of signing, secure timestamp time, or current time).  Document integrity verification confirms that the signed content hasn't changed after it was signed or that it has only changed in ways specifically permitted by the signer. 100

  • 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

100
7
Validating Signatures
When you receive a signed document, you may want to validate its signature(s) in order to verify who the
signer was, when they signed it, and what was actually signed. Depending on how you have configured
your application, validation may occur automatically.
However, understanding both how to validate a signature manually as well as what signature components
are analyzed during the validation process can facilitate trouble-free workflows and mitigate signature
status problems. Participants in signing workflows may also want to configure their environment to
streamline the validation process and control what kinds of content in signed documents can be run on
their machine.
The following sections provide validation details:
“Signature Validity Basics” on page 100
“Setting up Your Environment for Signature Validation” on page 102
“Validating Signatures Manually” on page 106
“Troubleshooting a Signature or Document Status” on page 115
“LiveCycle Dynamic Forms and the Warning Triangle” on page 121
“Save as 8.1 except that changes to document behavior are detected and invalidate an approval
signature: prior versions displayed a yellow triangle upon discovery of changes to document
behaviour.” on page 121
“Viewing and Comparing Changes and Versions” on page 122
7.1
Signature Validity Basics
As part of the signature validation process, Acrobat and Adobe Reader verify the signer’s identity as well as
the document’s integrity.
7.1.1
What Makes a Signature Valid?
Signature validity is determined by checking the signature’s digital ID certificate status (
is it valid and
trusted?
) and document integrity (
has it changed since being signed?
):
Authenticity verification confirms that the signer's certificate or that one of its parent certificates exists
in the validator’s list of trusted identities and that the signing certificate is valid at that point in time
according to the user's Acrobat or Reader configuration (time of signing, secure timestamp time, or
current time).
Document integrity verification confirms that the signed content hasn’t changed after it was signed or
that it has only changed in ways specifically permitted by the signer.