Novell SENTINEL 6.1 SP2, Руководство пользователя, Страница: 433 / 528

Identity Integration 433
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
The Solution also requires “identity-enabled” Collectors, which are available for download at the
standard Sentinel content download web site (http://support.novell.com/products/sentinel/
sentinel61.html)
.
After Sentinel and Identity Manager are installed, the Sentinel Driver for Identity Manager sends
identity and account information from the Identity Vault to the Sentinel Identity Vault Collector,
which populates the Sentinel database. The information is inserted into two new tables in Sentinel
6.1. These two tables are the Identity table (USR_IDENTITY) and the Account table
(USR_ACCOUNT ). For more information, see “
Sentinel Database Views for Oracle ” and “ Sentinel
Database Views for Microsoft SQL Server ” in Sentinel 6.1 Reference Guide .
The time required to initially populate the Sentinel database will depend on the amount of data in the
Identity Vault; identity information including photographs will require significantly more time to
load.
The Sentinel Driver for Identity Manager and Identity Vault Collector also keep the identity
information synchronized as information is updated in the Identity Vault during normal Identity
Manager operations.
After the identity information and account information are loaded in their respective tables with a
link between them, a map named
IdentityAccount
is generated automatically in the location
ESEC_HOME/DATA/MAP_DATA. The map contains the following information:
 Account Name

Authority
 Customer Name

Identity GUID
 Full Name

Department
 Job Title

Manager GUID
 Account Status
IMPORTANT: An identity can have multiple accounts but one account cannot be assigned to
multiple identities.
The identity map is automatically applied to all events from Collectors to look for an identical match
between the information in the event and key fields in the map. The table below shows the fields that
are populated if all of the map key fields and event data exactly match. These mappings are
automatically configured and are not editable.
Label
Populated by which Column
from IdentityAccount Map
Map Key Field : Event Label
InitUserDepartment Department Account Name : InitUserName
Authority : InitUserDomain
Customer Name : MSSPCustomerName