McAfee MEJCAE-AM-DA Product Guide - Page 58

Issuing X.509 certificates, Create a new key for issuing X.509 certificates

Page 58 highlights

Working with X.509 Certificates Issuing X.509 certificates Issuing X.509 certificates You can use E-Business Server to issue X.509 signature certificates to other users-acting as your own mini-Certificate Authority (CA). You may want to do the following: 1 Create a key to use for the sole purpose of issuing X.509 certificates (see Create a new key for issuing X.509 certificates on page 56). 2 Create a Root CA certificate (see Create a Root CA certificate on page 56). 3 Issue X.509 certificates to others by signing with the root certificate (see Sign public keys with the root certificate on page 57). Create a new key for issuing X.509 certificates Generate a new RSA or RSA Legacy key to use for the purpose of issuing X.509 certificates. For more information, see Creating a key pair on page 18. Note: You cannot create X.509 certificate signatures with a Diffie-Hellman/DSS key. Using an RSA key, you can certify any type of key. Create a Root CA certificate When creating a Root CA certificate, the key you are signing must be the same key you are signing with. This results in a self-signed X.509 certificate (root certificate) where the user-dn is the same as the issuer-dn. Once the Root CA certificate is created, it can be used to create other signing certificates. This is especially useful for corporations. For example, you can create a single root certificate (called "Root CA Certificate") for the company, and then use it to sign keys with certificates for departmental CA's (such as HR CA or Engineering CA). Finally, the departmental CA's could create certificates for end-users. Use the --key-sign --x509 option to create an X.509 certificate instead of a regular signature. Optionally, you can add certificate attributes using the --cert-attribute modifier to the new certificate you are creating. For more information on how to specify a certificate attribute, see Specifying certificate attributes on page 51. By default, an X.509 certificate is valid for one year from the certificate's creation date. When issuing an X.509 certificate, use the --start-date modifier to specify a future date as the beginning of the validity period and use the --expires-after modifier to specify the number of days you want the certificate to remain valid or a future date when the certificate will expire. When specifying a start or end date, enter the date in YYYY-MM-DD format. To create a root certificate: Enter the following: ebs --key-sign --x509 [--sign-with ] For example, if you create a key with the user ID "Root CA " and its key ID is "OxD7C74275", then you would enter the following: ebs --key-sign 0xD7C74275 --x509 --sign-with 0xD7C74275 You can find out more about the X.509 signature using the --sig-detail option. For the above example, you would enter the following: ebs --sig-detail 0xD7C74275 The following information appears: Signed Key : Root CA Signed User ID: Root CA E-Business Server™ 8.6 Product Guide 56

  • 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

E-Business Server
8.6
Product Guide
56
Working with X.509 Certificates
Issuing X.509 certificates
Issuing X.509 certificates
You can use E-Business Server to issue X.509 signature certificates to other users—acting as your own
mini-Certificate Authority (CA).
You may want to do the following:
1
Create a key to use for the sole purpose of issuing X.509 certificates (see
Create a new key for issuing
X.509 certificates
on page 56
).
2
Create a Root CA certificate (see
Create a Root CA certificate
on page 56
).
3
Issue X.509 certificates to others by signing with the root certificate (see
Sign public keys with the root
certificate
on page 57
).
Create a new key for issuing X.509 certificates
Generate a new RSA or RSA Legacy key to use for the purpose of issuing X.509 certificates. For more
information, see
Creating a key pair
on page 18
.
Note:
You cannot create X.509 certificate signatures with a Diffie-Hellman/DSS key. Using an RSA key, you can certify
any type of key.
Create a Root CA certificate
When creating a Root CA certificate, the key you are signing must be the same key you are signing with.
This results in a self-signed X.509 certificate (root certificate) where the user-dn is the same as the
issuer-dn.
Once the Root CA certificate is created, it can be used to create other signing certificates. This is especially
useful for corporations. For example, you can create a single root certificate (called “Root CA Certificate”)
for the company, and then use it to sign keys with certificates for departmental CA’s (such as HR CA or
Engineering CA). Finally, the departmental CA’s could create certificates for end-users.
Use the
--key-sign --x509
option to create an X.509 certificate instead of a regular signature.
Optionally, you can add certificate attributes using the
--cert-attribute
modifier to the new certificate you
are creating. For more information on how to specify a certificate attribute, see
Specifying certificate
attributes on page 51
.
By default, an X.509 certificate is valid for one year from the certificate’s creation date. When issuing an
X.509 certificate, use the
--start-date
modifier to specify a future date as the beginning of the validity
period and use the
--expires-after
modifier to specify the number of days you want the certificate to remain
valid or a future date when the certificate will expire. When specifying a start or end date, enter the date in
YYYY-MM-DD format.
To create a root certificate:
Enter the following:
ebs --key-sign <keyID> --x509 [--sign-with <keyID>]
For example, if you create a key with the user ID “Root CA <[email protected]>” and its key ID is
“OxD7C74275”, then you would enter the following:
ebs --key-sign 0xD7C74275 --x509 --sign-with 0xD7C74275
You can find out more about the X.509 signature using the
--sig-detail
option. For the above example, you
would enter the following:
ebs --sig-detail 0xD7C74275
The following information appears:
Signed Key
: Root CA <[email protected]>
Signed User ID: Root CA <[email protected]>