Adobe 22002486 Digital Signature User Guide - Page 30

Managing Certificate Trust and Trusted Identities

Page 30 highlights

3 Managing Certificate Trust and Trusted Identities As described in "What is a Digital ID?" on page 11, a digital ID consists of two main parts: a certificate with a public key and a private key. Participants in signing and certificate security workflows need to exchange the public part (the certificate) of their digital ID. Once you obtain someone's certificate and add it to your trusted identities list, you can encrypt documents for them. If their certificate does not already chain up to a trust anchor that you have specified, you can set the certificate's trust level so that you can validate the owner's signature. Understanding what a trusted identity is and how trust levels are set can help you set up streamlined workflows and troubleshoot problems. For example, you can add trusted identities ahead of time and individually set each certificate's trust settings. In enterprise settings where certificates are stored on a directory server, you may also be able to search for certificates to expand your list of trusted identities. For more information, refer to the following:  "What is a Trusted Identity?" on page 30  "Using Directory Servers to Add Trusted Identities" on page 38  "Adding Someone to Your Trusted Identity List" on page 32  "Managing Contacts" on page 42 3.1 What is Trust? The concept of "trust" is complex, and it may mean different things in different contexts. In Acrobat security workflows, trust can mean the following:  Trusting participants in your workflows: In both document security and signature workflows, you will need to trust those with whom you are sharing your documents. "Trusting an identity" means that you accept that someone's certificate actually represents a particular person or organization. It is official recognition on your part of the ownership and origin of the digital ID; that is, that the digital ID represents a specific entity.  Setting certificate trust levels: For those in your list of trusted identities, you will likely need to allow and disallow certain operations. You do this by associating (setting) trust levels with trusted identity's certificate. These trust levels define privileges that allow documents signed or certified by that identity to execute privileged operations on YOUR machine--things that cannot otherwise be done by documents you otherwise just open and display--for example, playing multimedia or executing JavaScript. Providing trust to a certificate should only be done if it is necessary and you want documents created and signed by the trusted identity to have higher levels of access to your machine. 3.2 What is a Trusted Identity? Digital signature and certificate security workflows both rely on certificates. Participants in signing workflows share their certificates ahead of time or embed them in a document. Participants in certificate 30

  • 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

30
3
Managing Certificate Trust and Trusted Identities
As described in
“What is a Digital ID?” on page 11
, a digital ID consists of two main parts: a certificate with
a public key and a private key. Participants in signing and certificate security workflows need to exchange
the public part (the certificate) of their digital ID. Once you obtain someone’s certificate and add it to your
trusted identities list, you can encrypt documents for them. If their certificate does not already chain up to
a trust anchor that you have specified, you can set the certificate’s trust level so that you can validate the
owner’s signature.
Understanding what a trusted identity is and how trust levels are set can help you set up streamlined
workflows and troubleshoot problems. For example, you can add trusted identities ahead of time and
individually set each certificate’s trust settings. In enterprise settings where certificates are stored on a
directory server, you may also be able to search for certificates to expand your list of trusted identities.
For more information, refer to the following:
“What is a Trusted Identity?” on page 30
“Using Directory Servers to Add Trusted Identities” on page 38
“Adding Someone to Your Trusted Identity List” on page 32
“Managing Contacts” on page 42
3.1
What is Trust?
The concept of “trust” is complex, and it may mean different things in different contexts. In Acrobat
security workflows, trust can mean the following:
Trusting participants in your workflows
: In both document security and signature workflows, you
will need to trust those with whom you are sharing your documents. “Trusting an identity” means that
you accept that someone’s certificate actually represents a particular person or organization.
It is
official recognition on your part of the ownership and origin of the digital ID; that is, that the digital ID
represents a specific entity.
Setting certificate trust levels
: For those in your list of trusted identities, you will likely need to allow
and disallow certain operations. You do this by associating (setting) trust levels with trusted identity’s
certificate. These trust levels define privileges that allow documents signed or certified by that identity
to execute privileged operations on YOUR machine--things that cannot otherwise be done by
documents you otherwise just open and display--for example, playing multimedia or executing
JavaScript. Providing trust to a certificate should only be done if it is necessary and you want
documents created and signed by the trusted identity to have higher levels of access to your machine.
3.2
What is a Trusted Identity?
Digital signature and certificate security workflows both rely on certificates. Participants in signing
workflows share their certificates ahead of time or embed them in a document. Participants in certificate