Microsoft Active Directory (AD)
- 1 minute to read
Microsoft Active Directory (AD) is a directory service for Windows domain networks that authenticates and authorizes all users and computers.
The Microsoft Active Directory (AD) adapter fetches devices from a specific DC through the LDAP protocol.
The Microsoft Active Directory (AD) adapter connection requires the following parameters:
- DC Address - The address of the Domain Controller (DC). Can be either IP or a valid DNS name.
- User Name and Password - A user with regular LDAP query rights and its password. The username should be in the form: DOMAIN\USERNAME. Please note that the prefix is case sensitive.
- DNS Address (optional) - By default we assume that the DC server is also a DNS server. This is not the case if the user specifies another DNS server for this Active Directory.
- Alternative DNS Suffix (optional) - Replace the device original DNS suffix for DNS resolving. For example, if the device name is windows8.acme.corp , and the Alternative DNS Suffix defined is 'acme-corp.lan', DNS resolving will be done for windows8.acme-corp.lan.
- Use SSL for connection (optional) - Use SLDAP (LDAP over SSL).
- CA File, Certificate File, Private Key File (optional) - If you choose to use SLDAP (LDAP over SSL), you need to add SSL certificates (CA File, PUBLIC and PRIVATE Certificates key files) to the credentials.
- Fetch Disabled Devices and Fetch Disabled Users (optional) - Select to fetch disabled devices or users. By default, Axonius fetch only enabled devices and users.
- Connect to Global Catalog (GC) - Select this option if the configured DC has a Global Catalog role.
- Organizational units whitelist (optional) - Set one ore more OUs so Axonius will fetch entities that reside only in the listed organizational units. Each item in the list should represent an 'OU' value of the desired OU DN. For example, for OU DN ("OU=Ireland Office,DC=acme,DC=corp"), specify 'Ireland Office'.
- Choose Instance - If you are using multi-nodes, choose the Axonius node that is integrated with the adapter. By default, the 'Master' Axonius node (instance) is used. For details, see Connecting Additional Axonius Nodes