HP 3PAR StoreServ 7200 2-node HP 3PAR CIM API Programming Reference (OS 3.1.2 - Page 11

Security, TCP Ports, Authentication - manual

Page 11 highlights

2 Security CAUTION: The CIM API is not part of the evaluated Common Criteria storage system configuration and should not be used when operating in Common Criteria mode. TCP Ports The CIM-API uses dedicated TCP ports for CIM-XML communications and server location information. Two ports are specified by the DMTF and registered with IANA for CIM-XML communications between management clients and any CIM Server. The following table lists the TCP Ports for the CIM-XML communication and service location protocols: Table 2 TCP Ports for CIM-XML Communication Protocol HTTP HTTPS Service Location (SLP) TCP Port 5988 (default value) 5989 (default value) 427 Authentication Authentication verifies the identity of an entity. Management clients accessing the CIM Server are authenticated using a request/challenge mechanism using HTTP Basic authentication. When a request is received from a management client, the CIM Server challenges the client to send a user name and password encoded in the HTTP Authorization header. The user names and passwords used are the same as those used by other management interfaces and are case sensitive. NOTE: CIM does not currently support LDAP user name and password authentication; only local user names and passwords are valid. Please see the HP 3PAR Concepts Guide for more information on local versus LDAP user credentials. The CIM Server uses Open SSL to support HTTPS connections. The server supports SSLv3 and TLSv1 by default and uses the default Open SSL cipher list only. For more about OpenSSL, refer to http:// www.openssl.org/docs. NOTE: Because Basic Authentication means that client user names and passwords are sent over the wire in unencrypted form, it is recommended that the authentication is carried out either over a physically secure private network, or in conjunction with HTTPS. Authorization Authorization determines whether an entity that has already been authenticated is allowed to perform a given operation. The CIM Server allows any authenticated user to retrieve CIM class and instance information. However, to invoke methods on CIM classes or instances, you must either have an Edit , Super, Administrator, or User permission level. Refer to the HP 3PAR Concepts Guide or the HP 3PAR InForm OS CLI Administrators Manual for complete information on authorization levels. NOTE: Access to certain information concerning volumes, CPGs, etc., is controlled by the InForm OS. Therefore, if a user authenticates with the CIM API and only has access to certain domains, only those objects in those domains returned by the InForm OS. In addition, operations on those objects also be constrained at the domain level. TCP Ports 11

  • 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
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309

2 Security
CAUTION:
The CIM API is not part of the evaluated Common Criteria storage system configuration
and should not be used when operating in Common Criteria mode.
TCP Ports
The CIM-API uses dedicated TCP ports for CIM-XML communications and server location information.
Two ports are specified by the DMTF and registered with IANA for CIM-XML communications
between management clients and any CIM Server. The following table lists the TCP Ports for the
CIM-XML communication and service location protocols:
Table 2 TCP Ports for CIM-XML Communication
TCP Port
Protocol
5988 (default value)
HTTP
5989 (default value)
HTTPS
427
Service Location (SLP)
Authentication
Authentication verifies the identity of an entity.
Management clients accessing the CIM Server are authenticated using a request/challenge
mechanism using HTTP Basic authentication. When a request is received from a management
client, the CIM Server challenges the client to send a user name and password encoded in the
HTTP Authorization header. The user names and passwords used are the same as those used by
other management interfaces and are case sensitive.
NOTE:
CIM does not currently support LDAP user name and password authentication; only local
user names and passwords are valid. Please see the
HP 3PAR Concepts Guide
for more information
on local versus LDAP user credentials.
The CIM Server uses Open SSL to support HTTPS connections. The server supports SSLv3 and TLSv1
by default and uses the default Open SSL cipher list only. For more about OpenSSL, refer to
h
t
tp://
w
w
w
.ope
ns
sl
.o
r
g/doc
s
.
NOTE:
Because Basic Authentication means that client user names and passwords are sent over
the wire in unencrypted form, it is recommended that the authentication is carried out either over
a physically secure private network, or in conjunction with HTTPS.
Authorization
Authorization determines whether an entity that has already been authenticated is allowed to
perform a given operation.
The CIM Server allows any authenticated user to retrieve CIM class and instance information.
However, to invoke methods on CIM classes or instances, you must either have an Edit , Super,
Administrator, or User permission level. Refer to the
HP 3PAR Concepts Guide
or the
HP 3PAR
InForm OS CLI Administrators Manual
for complete information on authorization levels.
NOTE:
Access to certain information concerning volumes, CPGs, etc., is controlled by the InForm
OS. Therefore, if a user authenticates with the CIM API and only has access to certain domains,
only those objects in those domains returned by the InForm OS. In addition, operations on those
objects also be constrained at the domain level.
TCP Ports
11