Adobe 22002486 Digital Signature User Guide - Page 176

Add to Trusted Identities, Use this certificate as a trusted root, Signed documents or data,

Page 176 highlights

Acrobat 9 Family of Products Security Feature User Guide Migrating and Sharing Security Settings Importing Application Settings with FDF Files 176 Tip: If Add to Trusted Identities is disabled, the identity is already on your Trusted Identities list. To change the trust settings, you must use the first method above. 5. On the Trust tab, select the trust options. In enterprise settings, an administrator should tell you which trust settings to use. Note: During an import action, recipients of the distributed trust anchor may be able to inherit its trust settings. Once you've verified the sender, you usually want to accept these settings so you can use the certificate they way the sender intended. Figure 140 Certificate trust settings  Use this certificate as a trusted root: Makes the certificate a trust anchor. The net result is that any certificates which chain up to this one will also be trusted for signing. At least one certificate in the chain (and preferably only one) must be a trusted root (trust anchor) to validate signatures and timestamps. Tip: There is no need to make end entity certificates trust anchors if they issued by a certificate holder whose certificate you have configured as a trust anchor. It is best practice to trust the topmost certificate that is reasonable to trust because revocation checking occurs on every certificate in a chain until that anchor is reached. For example, in a large organization, it is likely you would want to trust your company's certificate. If that certificate was issued by VeriSign, you would not want to make VeriSign a trusted root unless you wanted to trust every certificate that chains up to VeriSign.  Signed documents or data: Trusts the certificate for approval signatures. Tip: This setting is disabled because if the certificate is set as a trust anchor. Trust anchors are automatically trusted for approval signatures.  Certified documents: Trusts the certificate for certification signatures.

  • 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
Migrating and Sharing Security Settings
Security Feature User Guide
Importing Application Settings with FDF Files
176
Tip:
If
Add to Trusted Identities
is disabled, the identity is already on your Trusted Identities
list.
To change the trust settings, you must use the first method above.
5.
On the Trust tab, select the trust options. In enterprise settings, an administrator should tell you which
trust settings to use.
Note:
During an import action, recipients of the distributed trust anchor may be able to inherit
its trust settings. Once you’ve verified the sender, you usually want to accept these
settings so you can use the certificate they way the sender intended.
Figure 140
Certificate trust settings
Use this certificate as a trusted root
: Makes the certificate a trust anchor. The net result is that any
certificates which chain up to this one will also be trusted for signing. At least one certificate in the
chain (and preferably only one) must be a trusted root (trust anchor) to validate signatures and
timestamps.
Tip:
There is no need to make end entity certificates trust anchors if they issued by a certificate
holder whose certificate you have configured as a trust anchor. It is best practice to trust
the topmost certificate that is reasonable to trust because revocation checking occurs on
every certificate in a chain until that anchor is reached. For example, in a large
organization, it is likely you would want to trust your company’s certificate. If that
certificate was issued by VeriSign, you would not want to make VeriSign a trusted root
unless you wanted to trust every certificate that chains up to VeriSign.
Signed documents or data
: Trusts the certificate for approval signatures.
Tip:
This setting is disabled because if the certificate is set as a trust anchor. Trust anchors are
automatically trusted for approval signatures.
Certified documents
: Trusts the certificate for certification signatures.