HP 635n Practical IPsec Deployment for Printing and Imaging Devices - Page 190

Unfortunately, the Enterprise

Get HP 635n - JetDirect IPv6/IPsec Print Server PDF manuals and user guides
UPC - 882780301016
View all HP 635n manuals
Add to My Manuals
Save this manual to your list of manuals

Page 190 highlights

The "Certificate Export Wizard" launches - Press "Next" Since we are going to import this certificate into Jetdirect, we need to export the private key as well. Select "Yes, export the private key" and then click "Next". NOTE: In most cases, when exporting a certificate, you will not want to export the private key. The private key is best kept on the machine that generated it and never moved. This functionality is usually done by generating a Certificate Signing Request (CS) on Jetdirect. The CSR process on Jetdirect creates a public and private key pair and includes the public key with the CSR while the private key is stored in flash and never exposed external to the Jetdirect device. The CSR is then sent to the Certificate Authority which issues a certificate based upon the information in the request. This certificate would be simply "installed" in Jetdirect and not "imported". Unfortunately, the Enterprise CA modifies the certificate in a way that is not compatible with Jetdirect's CSR and this resulted in Jetdirect refusing to accept the certificate during its installation. Jetdirect has since addressed this problem starting with version V.36.11. Using V.36.11 and later, certificates issued from the 190

  • 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
  • 190
  • 191
  • 192
  • 193
190
The
“Certificate
Export
Wizard”
launches –
Press “Next”
Since we are
going to
import this
certificate into
Jetdirect, we
need to export
the private key
as well.
Select
“Yes, export
the private
key” and then
click “Next”.
NOTE: In most cases, when exporting a certificate, you will not want to export the private key.
The
private key is best kept on the machine that generated it and never moved. This functionality is
usually done by generating a Certificate Signing Request (CS) on Jetdirect.
The CSR process on
Jetdirect creates a public and private key pair and includes the public key with the CSR while the
private key is stored in flash and never exposed external to the Jetdirect device.
The CSR is then sent
to the Certificate Authority which issues a certificate based upon the information in the request.
This
certificate would be simply “installed” in Jetdirect and not “imported”.
Unfortunately, the Enterprise
CA modifies the certificate in a way that is not compatible with Jetdirect’s CSR and this resulted in
Jetdirect refusing to accept the certificate during its installation. Jetdirect has since addressed this
problem starting with version V.36.11.
Using V.36.11 and later, certificates issued from the