Dell Powerconnect W-ClearPass Hardware Appliances W-ClearPass Policy Manager 6 - Page 99

Authorization, Posture Compliance, Audit End-hosts, Profile Endpoints, NOTE: Authentication, Posture

Page 99 highlights

Service Type Description/ Available Policy Components (in tabs)/ Service Rule (in Rules Editor)/ Service-specific policy components (called out with legend below) Template for any kind of RADIUS request. Rules can be added to handle RADIUS requests that sends any type of standard or vendor-specific attributes. RADIUS Enforcement [Generic] NOTE: No default rule associated with this service type. Rules can be added to handle any type of standard or vendor-specific RADIUS attributes (any attribute that is loaded through the prepackaged vendor-specific or standard RADIUS dictionaries, or through other dictionaries imported into Policy Manager). You can click on the Authorization, Posture Compliance, Audit End-hosts and Profile Endpoints options to enable additional tabs. Refer to the "802.1X Wireless " on page 92 service type for a description of the other tabs. Template for any kind of RADIUS request that needs to be proxied to another RADIUS server (a Proxy Target). RADIUS Proxy NOTE: No default rule is associated with this service type. Rules can be added to handle any type of standard or vendor-specific RADIUS attributes. Typically, proxying is based on a realm or domain of the user trying to access the network. NOTE: Authentication, Posture, and Audit tabs are not available for this service type. Role mapping rules can be created based on the RADIUS attributes that are returned by the proxy target (using standard or vendor-specific RADIUS attributes). The servers to which requests are proxied are called Proxy Targets. Requests can be dispatched to the proxy targets randomly; over time these requests are Load Balanced. Instead, in the Failover mode, requests can be dispatched to the first proxy target in the ordered list of targets, and then subsequently to the other proxy targets, sequentially, if the prior requests failed. When you Enable proxy for accounting requests accounting requests are also sent to the proxy targets. Dell Networking W-ClearPass Policy Manager 6.0 | User Guide 99

  • 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
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372

Service Type
Description/ Available Policy Components (in tabs)/ Service Rule (in Rules Editor)/
Service-specific policy components (called out with legend below)
RADIUS
Enforcement
[Generic]
Template for any kind of RADIUS request. Rules can be added to handle RADIUS requests that
sends any type of standard or vendor-specific attributes.
NOTE:
No default rule associated with this service type. Rules can be added to handle any type
of standard or vendor-specific RADIUS attributes (any attribute that is loaded through the pre-
packaged vendor-specific or standard RADIUS dictionaries, or through other dictionaries
imported into Policy Manager).
You can click on the
Authorization
,
Posture Compliance
,
Audit End-hosts
and
Profile Endpoints
options to enable additional tabs. Refer to the
"802.1X Wireless " on page 92
service type for a
description of the other tabs.
RADIUS Proxy
Template for any kind of RADIUS request that needs to be proxied to another RADIUS server (a
Proxy Target).
NOTE:
No default rule is associated with this service type. Rules can be added to handle any
type of standard or vendor-specific RADIUS attributes. Typically, proxying is based on a realm or
domain of the user trying to access the network.
NOTE: Authentication
,
Posture
, and
Audit
tabs are not available for this service type.
Role mapping rules can be created based on the RADIUS attributes that are returned by the
proxy target (using standard or vendor-specific RADIUS attributes).
The servers to which requests are proxied are called
Proxy Targets
. Requests can be dispatched
to the proxy targets randomly; over time these requests are
Load Balanced
. Instead, in the
Failover mode, requests can be dispatched to the first proxy target in the ordered list of targets,
and then subsequently to the other proxy targets, sequentially, if the prior requests failed. When
you
Enable proxy for accounting requests
accounting requests are also sent to the proxy targets.
Dell Networking W-ClearPass Policy Manager 6.0 | User Guide
99