In order to perform a successful connection to your Active Directory server, we just need the following information and that's it! 

  1. LDAP URL: This is the IP address of your Active Directory server. 
  2. Default Base DN: This is the domain name. You should provide it to us in the form (DC=’domain’, DC=’.com’) , where domain is the name of your domain and .com would be the termination of the domain which can vary depending on the configuration of your Active Directory services.
  3. Username and Password: This username and password has to be from a user who has the access to read the information of the Directory.

Once we have a successful connection, it will enable us to populate your AlertFind instance with the following information : 

  • UserID 
  • Display Name 
  • First Name 
  • Last Name 
  • Email 
  • Home Phone 
  • Mobile Phone 
  • Company URL 
  • Job Title
  • Company 
  • Department 
  • Country 
  • State 
  • City 
  • Street Address 
  • Zip Code 
  • Office PO Box 
  • Office Location

How does our Active Directory On Premises connector works :
The below graphic explains the various nodes involved in the transition of data from your Active Directory instance to AlertFind.

Detailed Steps Explaining Above Graphic :

  1. AD On Premise connector fetches the User Information stored in your AD On Premise instance via API.
  2. Based on your chosen frequency, our connector running on AWS Lambda, fetches data from AD On Premise.
  3. At this stage, data goes through the validation and processing and is finally transformed into a CSV.
  4. The CSV is compressed to a Zip file and sent to AlertFind API via the AlertFind connector running on AWS lambda.

Data Storage Nodes in The Graphic Above:

  1. Node 5 : Refers to Apache Cassandra Cluster which stores the data for execution purposes. It has a TTL of 7 days after workflow execution has finished.
  2. Node 6 : Refers to Elastic Search Cluster used for indexing data for 30 days so that it can be searched within the logs interface.
  3. Data Safety : All Data is encrypted in transit via HTTPS, using TLS 1.3 encryption internally. Sensitive customer data, such as access tokens, usernames, passwords are encrypted at rest using Amazon Key Management Service (KMS), which uses FIPS 140-2 validated hardware security modules.

We encourage you to keep searching the connector that suits your needs in our main AlertFind Connector List under the section System of Records Integrations by clicking the button below.

Did this answer your question?