Adobe 22002486 Digital Signature User Guide - Page 105

Validating Signatures with Timestamps and Certificate Policies

Page 105 highlights

Acrobat 9 Family of Products Security Feature User Guide Validating Signatures Validating Signatures with Timestamps and Certificate Policies 105 Figure 71 Trusting Windows root certificates 2. Specify the trust level for all root certificates in the Windows Certificates Store:  Validating signatures: Certificates will be trusted for approval signature validation.  Validating certified documents: Certificates will be trusted for certification signature validation. 3. Choose OK, and exit the preferences dialogs. 7.2.4 Validating Signatures with Timestamps and Certificate Policies Certificate policies can be used with timestamps, but they can only be verified on the client end, not on the server end. That is, a timestamped signature can not be sent with CRL request with a specific policy OID; however, the client can require that the server response include a specified policy constraint. If the timestamp server returns a response that doesn't include a matching policy OID, then the client would reject the timestamp and it's status would be invalid. The user interface shows the following:  The signature could be valid, but it's validated at the current time. The Signature pane shows the appropriate icon.  The timestamp is invalid. The Summary tab of the Signature Properties dialog shows a red X The require a timestamp to be associated with a particular certificate policy: 1. Configure your application to validate signatures using Secure Time as described in "Setting Digital Signature Validation Preferences" on page 103. 2. Configure a policy constraint for a trust anchor in your trusted identities list: Note: xxxx: question: Am I choosing the certificate for the timestamp server I have previously added to my trusted identities list? 1. Choose Advanced > Managed Trusted Identities. 2. In the Display drop down list, choose Certificates. 3. Select the timestamp server's certificate that will be used as a trust anchor.

  • 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
Validating Signatures with Timestamps and Certificate Policies
105
Figure 71
Trusting Windows root certificates
2.
Specify the trust level for all root certificates in the Windows Certificates Store:
Validating signatures
: Certificates will be trusted for approval signature validation.
Validating certified documents
: Certificates will be trusted for certification signature validation.
3.
Choose
OK,
and exit the preferences dialogs.
7.2.4
Validating Signatures with Timestamps and Certificate Policies
Certificate policies can be used with timestamps, but they can only be verified on the client end, not on
the server end. That is, a timestamped signature can not be sent with CRL request with a specific policy
OID; however, the client can require that the server response include a specified policy constraint. If the
timestamp server returns a response that doesn't include a matching policy OID, then the client would
reject the timestamp and it's status would be invalid. The user interface shows the following:
The signature could be valid, but it's validated at the current time. The Signature pane shows the
appropriate icon.
The timestamp is invalid. The Summary tab of the Signature Properties dialog shows a red X
The require a timestamp to be associated with a particular certificate policy:
1.
Configure your application to validate signatures using Secure Time as described in
“Setting Digital
Signature Validation Preferences” on page 103
.
2.
Configure a policy constraint for a trust anchor in your trusted identities list:
Note:
xxxx: question: Am I choosing the certificate for the timestamp server I have previously added to
my trusted identities list?
1.
Choose
Advanced > Managed Trusted Identities
.
2.
In the
Display
drop down list, choose Certificates.
3.
Select the timestamp server’s certificate that will be used as a trust anchor.