Cisco SPA525G Administration Guide - Page 148

Obtaining a Server Certificate, Qualified Domain Name syntax. During SSL authentication handshake,

Page 148 highlights

7 Provisioning Basics Using HTTPS each individual endpoint. A certificate authority root certificate capable of authenticating the device client certificate is given to each service provider. This authentication path allows the provisioning server to reject unauthorized requests for configuration profiles. Obtaining a Server Certificate To obtain a server certificate: STEP 1 Contact a Cisco/Linksys support person who will work with you on the certificate process. STEP 2 Generate a private key that will be used in a CSR (Certificate Signing Request). This key is private and you do not need to provide this key to Cisco support. Use open source "openssl" to generate the key. For example: openssl genrsa -out 1024 STEP 3 Generate CSR a that contains fields that identify your organization, and location. For example: openssl req -new -key -out You must have the following information: • Subject field-Enter the Common Name (CN) that must be a FQDN (Fully Qualified Domain Name) syntax. During SSL authentication handshake, the SPA9000 verifies that the certificate it receives is from the machine that presented it. • Server's hostname-For example, provserv.domain.com. • Email address-Enter an email address so that customer support can contact you if needed. This email address is visible in the CSR. STEP 4 Email the CSR (in zip file format) to the Cisco/Linksys support person. The certificate is signed by Cisco and given to you. 146 Cisco SPA and Wireless IP Phone Administration Guide

  • 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
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280

Provisioning Basics
Using HTTPS
146
Cisco SPA and Wireless IP Phone Administration Guide
7
each individual endpoint. A certificate authority root certificate capable of
authenticating the device client certificate is given to each service provider. This
authentication path allows the provisioning server to reject unauthorized requests
for configuration profiles.
Obtaining a Server Certificate
To obtain a server certificate:
STEP 1
Contact a Cisco/Linksys support person who will work with you on the certificate
process.
STEP 2
Generate a private key that will be used in a CSR (Certificate Signing Request).
This key is private and you do not need to provide this key to Cisco support. Use
open source "openssl" to generate the key. For example:
openssl genrsa -out <file.key> 1024
STEP 3
Generate CSR a that contains fields that identify your organization, and location.
For example:
openssl req -new -key <file.key> -out <file.csr>
You must have the following information:
Subject field—Enter the Common Name (CN) that must be a FQDN (Fully
Qualified Domain Name) syntax. During SSL authentication handshake, the
SPA9000 verifies that the certificate it receives is from the machine that
presented it.
Server's hostname—For example, provserv.domain.com.
Email address—Enter an email address so that customer support can
contact you if needed. This email address is visible in the CSR.
STEP 4
Email the CSR (in zip file format) to the Cisco/Linksys support person. The
certificate is signed by Cisco and given to you.