IBM BJ0NJML Integration Guide - Page 199

Interface Table Security, Outbound Router Handler Security, Object-Level Authorization

Page 199 highlights

Interface Table Security T processObjectStructure(..) T routeData(..) To run these methods, the caller must retrieve a valid UserInfo object and pass it to the method to gain access to the secure layer. A UserInfo object is a serialized object that contains user details (user, password, locale, language, and time zone information). The system uses the UserInfo object for security purposes. The system uses Java RMI/JRMP. You can communicate to the system services by using a secure version of JRMP protocol using SSL. Interface Table Security Interface tables use the default database authentication and authorization. If authentication and authorization are in effect, external programs that read or write to the interface tables must provide proper authorization. To read from and write to the interface tables, the USERNAME and PASSWORD values are configured for the endpoint that implements the interface table handler. Outbound Router Handler Security The outbound router handlers have support for authorization and confidentiality. The enterprise bean, HTTP, JMS, Web service, and interface table handlers have support for security. Object-Level Authorization The system provides object-level authorization based on the security configuration set within the system. If an object or attribute is marked as readonly or hidden, then inbound message data processing is limited to data object queries. You cannot insert, update, or delete data in that object. The authorization level for a business object and object attribute can be configured in the Data Restrictions tab in the Security Groups application. Except for standard services, integration messages are not processed according to application-level authorization. The authorization that is used for system users controls the standard service authorization. A signature option can be assigned to a standard service to limit authorization to the users or groups that have authorization for a selected option. Security 185

  • 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

Interface Table Security
Security
185
processObjectStructure(..)
routeData(..)
To run these methods, the caller must retrieve a valid UserInfo object and pass it
to the method to gain access to the secure layer.
A UserInfo object is a serialized object that contains user details (user, password,
locale, language, and time zone information). The system uses the UserInfo object
for security purposes.
The system uses Java RMI/JRMP. You can communicate to the system services by
using a secure version of JRMP protocol using SSL.
Interface Table Security
Interface tables use the default database authentication and authorization. If
authentication and authorization are in effect, external programs that read or
write to the interface tables must provide proper authorization. To read from and
write to the interface tables, the USERNAME and PASSWORD values are
configured for the endpoint that implements the interface table handler.
Outbound Router Handler Security
The outbound router handlers have support for authorization and confidentiality.
The enterprise bean, HTTP, JMS, Web service, and interface table handlers have
support for security.
Object-Level Authorization
The system provides object-level authorization based on the security
configuration set within the system. If an object or attribute is marked as read-
only or hidden, then inbound message data processing is limited to data object
queries. You cannot insert, update, or delete data in that object. The authorization
level for a business object and object attribute can be configured in the Data
Restrictions tab in the Security Groups application.
Except for standard services, integration messages are not processed according to
application-level authorization.
The authorization that is used for system users controls the standard service
authorization. A signature option can be assigned to a standard service to limit
authorization to the users or groups that have authorization for a selected option.