MS ActiveDirectory ConfigGuide
MS ActiveDirectory ConfigGuide
Legal Notices
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Copyright Notice
Copyright 2001-2024 Open Text.
The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be
set forth in the express warranty statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or
omissions contained herein. The information contained herein is subject to change without notice.
Trademark Notices
“OpenText” and other Open Text trademarks and service marks are the property of Open Text or its affiliates. All other
trademarks or service marks are the property of their respective owners.
Support
Contact Information
Phone A list of phone numbers is available on the Technical Support
Page: https://softwaresupport.softwaregrp.com/support-contact-information
Publication Status 21
Page 3 of 22
ESM
This guide describes installing the ESM and configuring the device for data collection.
Microsoft’s Active Directory allows IT administrators to centrally manage objects in an
enterprise. These objects include resources (such as printers), users (such as individual users
and user groups), and services (such as e-mail).
The ESM extracts the user identity information (or Actor data) from the Active Directory LDAP,
then uses that data to populate ArcSight ESM with resources. The Actor resource is populated
dynamically, meaning that, as the identity data changes in Active Directory, the resource data
in ESM is automatically updated.
Note: The connector only supports queries on the same domain as the user accounts. The
connector does not support queries across domains.
ESM Page 4 of 22
Actor Model Import Connector for Microsoft Active Directory Configuration Guide
ESM
Note: For read and access privileges for the connector, a basic AD user ID will work.
Connector Installation
Note: Use a non-root account to install the Active Directory Model Import Connector.
Note: The options for FIPS and remote management are not applicable at this time when
“Set Global Parameters” is selected for this connector.
3. See Modifying Connector Settings in the SmartConnector User Guide for setting preferred
IP version.
4. Select Actor Model Import Connector for Microsoft Active Directory. Click Next.
5. On the parameter details screen, enter values for the following parameters:
Parameter Details
Parameter Description
Active Directory Enter the host name or an IP address of the Active Directory server.
machine host
name or IP
Security protocol Select ssl (encrypted) or non-ssl (default, non-encrypted). Also, select an Active Directory
port.
Active Directory Enter the port; 636 for SSL security protocol, or 389 for non-SSL security protocol.
port
Administrator Enter the name of a user from the Domain Admins group that the SmartConnector can use
user for Active to access Active Directory data.
Directory
AD Enter the password for the user you specified as the Administrator user for the previous
administrator's parameter.
password
AD query paused Leave the default value of 'true.' After the connector is started from the ESM Console, this
value changes to 'false' automatically so that the AD query continues automatically
whenever the connector restarts.
AD query Enter the time interval after which the SmartConnector polls the Active Directory server
interval for updates. The default value is 10. The minimum value that can be specified is 1.
(in minutes)
AD search base Enter the search base of the Active Directory domain; for example, DC=company, DC=com.
IDM Identifier Enter a name of your choosing to identify the IDM system from which the connector is
carrying data. (e.g., “company-dc.company.com”)
Click Enter.
6. On the type of destination screen, verify that ArcSight Manager (encrypted) is selected
and then click Next.
7. On the destination parameters screen, enter or select values for the parameters and click
Next. The connector details screen displays.
8. Enter the details for your connector. Click Next and complete the installation wizard.
Tip: After completing the SmartConnector installation wizard, be sure to manually configure
the connector for the type of SSL certificate your ArcSight Manager is using. See the
ArcSight ESM Administrator's Guide for complete information.
For some connectors, a system restart is required before the configuration settings you made
take effect. If a System Restart window displays, read the information and initiate the system
restart operation.
Caution: Save any work on your computer or desktop and shut down any other running
applications (including the Command Center, if it is running), then shut down the system.
To uninstall the connector, or for connector upgrade instructions, see the SmartConnector
User's Guide.
Note: For more information about Actors, including the maximum number of actor models
supported in ArcSight ESM, see the Command Center online help.
To change the Actor batching time or size, you can add the following properties to
agent.properties (located at $ARCSIGHT_HOME\current\user\agent).
l buildmodeldelay controls the batching time. This dictates how long in milliseconds the
wait before sending a batch of Actors to ESM.
l maxeventsbeforebuild controls the batching size. This dictates how many Actors can be
received before sending a batch of Actors to ESM.
For example, the following properties set the batching time to 10 seconds and the batching
size to 2500 Actors:
agent.component[35].buildmodeldelay=10000
agent.component[35].maxeventsbeforebuild=2500
The trigger for sending user (or Actor) data to ESM can be controlled through either a counter
(the indicator of batch size) or timer (the indicator of elapsed time between batches). Priority
is given to the first satisfied condition. For example, if the batch size achieves the maximum
number of Actors allowed before the default time is exceeded, the Actor data is sent based on
batch size. Conversely, if the defined time is reached before the defined buffer size is achieved,
the data is sent to ESM based on the allotted time. After the batch is sent to ESM, the timer
and counter revert back to zero in preparation for the next batch.
Caution: If your deployment exceeds 10K actors with an average of 5 groups per user, we
recommend modifying your minimum heap setting to 2GB. The maximum heap size should be
6GB, depending on available memory.
automatically active when a host is re-started. If installed as a UNIX daemon, the connector
runs automatically when the host is re-started. For information about connectors running as
Windows services or UNIX daemons, see the ArcSight SmartConnector User's Guide.
For connectors installed standalone, to run all installed connectors on a particular host, open a
command window, go to $ARCSIGHT_HOME\current\bin and run:
arcsight agents
When you run the connector, it is started in Pause mode; it does not continue until you instruct
it to do so through the ArcSight Console. Before doing so, set up a user for the connector, as
described in the next section.
To view the connector log, read the file:
$ARCSIGHT_HOME\current\logs\agent.log
Tip: On Windows platforms, connectors can also be run using shortcuts and optional Start menu
entries.
2. Configure filtering conditions by group type by entering each group type separated by the
OR operator. Right-click the connector name, then Configure, Default, and Filters.
The following is an example of filtering OUT groups by group Type. By default, the
connector does not filter OUT groups by type.
4. Right-click the connector and choose Send Commands -> Model Import Connector-> Start
Import.
The initial import begins.
Note: This initial import of data cannot be stopped until the transfer is complete. If you
discover a configuration error mid-process, stop the connector, make your configuration
changes, then reload the Active Directory information. See "Reloading Active Directory
Information" on page 17 for detailed instructions.
5. After the import completes, configure the authenticators mapping table in ArcSight
Console with the list of authenticators used in your environment. For detailed instructions,
see the “Configuring Actors (for Administrators)” section of the ArcSight Console online
help.
Account Specifier
The account specifier, for Active Directory accounts, has the following default values:
l sAMAccountName
l mail
l distinguishedName
l userPrincipalName
You can add or remove attributes by modifying the accountspecifier property. To add or
delete attributes, the accountspecifier property is added to agent.properties (located at
$ARCSIGHT_HOME\current\user\agent). For example:
agents[0].accountspecifier=givenName,title
If used, this property should be specified before the initial import since account import
behavior is affected by the accountspecifier property. It is not advisable to add or delete
attributes unless you are certain about why you are making the changes. A typical use case
would be if your LDAP domain has a limitation needing a set of attributes other than the
default attributes to identify an account.
Authenticator
The authenticator, for Active Directory accounts, can be controlled by the authenticator
property. The default value is derived from the DC components of the search base, but it can
be modified with the authenticator property.
To change the account authenticator, add the authenticator property to agent.properties
(located at $ARCSIGHT_HOME\current\user\agent). For example:
agents[0].authenticator=mf.net.local
If used, this property should be specified before the initial import since account import
behavior is affected by the authenticator property. It is not advisable to add the property
unless you are certain about why you are adding the property. A typical use case would be to
have one authenticator across multiple domains.
For Windows, the path starts with %ARCSIGHT_HOME% and uses back slashes. For example:
l Linux: $ARCSIGHT_HOME/current/user/agent/agent.properties
l Windows: %ARCSIGHT_HOME%\current\user\agent\agent.properties
The agent.properties file is a plain text file. Use the appropriate editor for your operating
system to edit the content. For example, use Notepad for Windows and vi for Linux. Any
modifications to the agent.properties file should be performed very carefully with
knowledge of how parameters operate. This way, you would avoid inadvertently altering the
behavior of the SmartConnector.
Caution: If you wish to re-add an attribute that you did not import initially, you must re-import
the entire set. See "Reloading Active Directory Information" on page 17 for detailed instructions.
Authenticator Page 15 of 22
Actor Model Import Connector for Microsoft Active Directory Configuration Guide
ESM
Locate the attributelist parameter to remove any unneeded attribute fields. Do not remove
a required attribute (the first 15 attributes of the following list), as they are the minimum
required for the system to properly operate.
objectGUID
whenCreated
whenChanged
memberof: Member of
member: Member
sAMAccountName: User ID
mail: Email Address
distinguishedName: Distinguished Name
userPrincipalName: User Principal Name
cn: Full Name
givenName: First Name
sn: Last Name
department: Department
userAccountControl: Status
employeeType: Employee Type
Tip: The employeeType attribute is not available in the native Microsoft Management Console.
To use the resources based upon Employee Type, the attribute must be set using a tool such as
ADSI edit. ADSI Edit is an MMC snap-in that acts as a low-level editor for Active Directory. This
tool is included when you install Microsoft Windows Server Support Tools from the product CD
or from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=100114). For
information about how to install Windows Support Tools from the product CD, see Install
Windows Support Tools at http://go.microsoft.com/fwlink/?LinkId=62270.
Caution: If you wish to re-add an attribute you mistakenly deleted, you must re-import the
entire set. See "Reloading Active Directory Information" below for detailed instructions.
The group name will be a number and the groupTypeName will be this translation:
groupTypeName groupName
Built-In -2147483643
Domain Local Security -2147483644
Global Security -2147483646
Universal Security -2147483640
Domain Local Distribution 2
Global Distribution 4
Universal Distribution 8
Caution: Do not delete Actors outside of this top level directory. If you are deleting a large
number of actors, see "Best Practices for Deleting a Large Number of Actors" below.
Caution: Performing this action does not remove all the Actor data and history.
5. From the following directory, delete all files starting with ps.user and ps.group:
$ARCSIGHT_HOME/user/agent/agentdata
6. From this same directory ($ARCSIGHT_HOME/user/agent/agentdata), delete the
{connector_id}.status.init.import file.
7. Restart the connector.
dbconmanager.provider.logger.pool.maxcheckout=36000
3. In the ArcSight Console, stop the Actor Model Import Connector for Microsoft Active
Directory. Right-click the connector and choose Send Commands > Model Import
Connector > Stop.
4. Stop the ArcSight Manager.
5. Delete the actor data from the database. Run the following command in
/opt/arcsight/logger/current/arcsight/bin:
Where <username> and <password> are the database user name and password that were
set when you configured the database. Per MySQL conventions, omit the space between -
p and the password.
If any of the delete commands fail with the SQL message ERROR 1205 (HY000): Lock
wait timeout exceeded; try restarting transaction, retry the delete command
after a few seconds.
6. Start the ArcSight Manager.
7. From the ArcSight Console, delete any remaining actors from the Actor group.
8. On the machine where the Actor Model Import Connector for Microsoft Active Directory is
installed, delete the following files from /user/agent/agentdata:
*ps files
*status.init files
9. Restart the Actor Model Import Connector for Microsoft Active Directory.
Publication Status
Released: January 2024