Adobe 22002486 Digital Signature User Guide - Page 121

LiveCycle Dynamic Forms and the Warning Triangle

Page 121 highlights

Acrobat 9 Family of Products Security Feature User Guide Validating Signatures Troubleshooting a Document Integrity Problem 121  Right click on a signature and choose View Signed Version or choose Click to view this version in the Signature pane to view the version that signed. Review the status for this version. For details, see Chapter 8, "Document Integrity and Preview Mode".  Open the Form Fields Filled In, or Annotations Created or Modified item to see which fields or annotations were changed or added.  Review the document changes as described in "Viewing a List of Post-Signing Modifications" on page 122.  Perform a page by page and line by line comparison of the problem version with any of the signed versions. For details, see "Comparing a Signed Version to the Current Version" on page 123. 3. Based on the discovered document changes, determine whether you should trust the document. 4. If the status is invalid (displays a red X), illegal changes have been made to the document, there is no way to undo those changes without further changing the document illegally. Do the following:  Contact the sender to resolve the problem. Secure the workflow so that illegal changes are prevented.  Policy restrictions on a trust anchor can result in signature invalidity. If you have set a policy restriction, determine if that is the problem remove the restriction. 5. If you still cannot pinpoint the problem, or you need help with some of the steps above, read the following:  "Troubleshooting Digital ID Certificates" on page 116 7.5.2.1 LiveCycle Dynamic Forms and the Warning Triangle Document Integrity Checks for 8.0 Acrobat 8.0 considers all scripts executed during document construction to potentially modify the document even if it's designed with a read-only query or some other "no change" action. The presence and detection of those scripts would trigger Acrobat to display the yellow warning triangle, thereby indicating that the document may have changed. Scripts that invalidate certification would be prevented from executing so it would not be possible for such scripts to invalidate certifying signatures. Document Integrity Checks for 8.1 Acrobat 8.1 does not consider all scripts executed during document construction to potentially modify the document, and the detection of a script does not cause Acrobat to flag the document as changed. The application compares the digitally signed and current document versions to determine if the current version has been modified. If there is a change, then a warning triangle appears on the approval signature. For example, the following changes are detected:  Changes to the value of an LiveCycle form field (including clearing it).  Changes to the properties of an LiveCycle form field. Document Integrity Checks for 9.0  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.

  • 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
Validating Signatures
Security Feature User Guide
Troubleshooting a Document Integrity Problem
121
Right click on a signature and choose
View Signed Version
or choose
Click to view this version
in
the Signature pane to view the version that signed. Review the status for this version. For details, see
Chapter 8, “Document Integrity and Preview Mode”
.
Open the
Form Fields Filled In, or Annotations Created or Modified
item to see which fields or
annotations were changed or added.
Review the document changes as described in
“Viewing a List of Post-Signing Modifications” on
page 122
.
Perform a page by page and line by line comparison of the problem version with any of the signed
versions. For details, see
“Comparing a Signed Version to the Current Version” on page 123
.
3.
Based on the discovered document changes, determine whether you should trust the document.
4.
If the status is invalid (displays a red X), illegal changes have been made to the document, there is no
way to undo those changes without further changing the document illegally. Do the following:
Contact the sender to resolve the problem. Secure the workflow so that illegal changes are
prevented.
Policy restrictions on a trust anchor can result in signature invalidity. If you have set a policy
restriction, determine if that is the problem remove the restriction.
5.
If you still cannot pinpoint the problem, or you need help with some of the steps above, read the
following:
“Troubleshooting Digital ID Certificates” on page 116
7.5.2.1
LiveCycle Dynamic Forms and the Warning Triangle
Document Integrity Checks for 8.0
Acrobat 8.0 considers all scripts executed during document construction to potentially modify the
document even if it’s designed with a read-only query or some other “no change” action. The presence
and detection of those scripts would trigger Acrobat to display the yellow warning triangle, thereby
indicating that the document may have changed. Scripts that invalidate certification would be prevented
from executing so it would not be possible for such scripts to invalidate certifying signatures.
Document Integrity Checks for 8.1
Acrobat 8.1 does not consider all scripts executed during document construction to potentially modify the
document, and the detection of a script does not cause Acrobat to flag the document as changed. The
application compares the digitally signed and current document versions to determine if the current
version has been modified. If there is a change, then a warning triangle appears on the approval signature.
For example, the following changes are detected:
Changes to the value of an LiveCycle form field (including clearing it).
Changes to the properties of an LiveCycle form field.
Document Integrity Checks for 9.0
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.