CSOAR-2927 - Active Directory V2 setup

docs/platform-services/automation-service/app-central/integrations/active-directory-v2.md

@@ -41,6 +41,99 @@ Compatibility notice:
 
 * [LDAP3](https://github.com/cannatag/ldap3/blob/master/LICENSE.txt)
 
+## Active Directory V2 configuration
+
+### Prerequisites
+
+* An [Automation Bridge](/docs/platform-services/automation-service/automation-service-bridge/) installation.
+* A Microsoft Windows Server with Active Directory Domain Services (AD DS) configured.
+
+### Setting up Microsoft Windows Server (optional)
+
+If an existing Windows Server is not available, follow these steps to set up a new one in AWS:
+1. Create a Microsoft Windows Server 2019 Instance on AWS.
+   1. Launch a new AWS EC2 instance.
+   1. Choose **Microsoft Windows Server 2019 Base** as the AMI.
+   1. Configure instance settings (for example, instance type, storage, security groups).
+   1. Assign a key pair for secure access.
+   1. Deploy the instance and wait for it to be fully initialized.
+1. Configure the Windows Server.
+   1. Connect to the instance using Remote Desktop Protocol (RDP).
+   1. Once logged in, open **Server Manager**.
+1. Install Active Directory Domain Services (AD DS).
+   1. In **Server Manager**, select **Add roles and features**.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/active-directory-v2/active-directory-v2-add-roles-and-features.png')} style={{border:'1px solid gray'}} alt="Add roles and features" width="600"/>
+   1. Choose **Role-based or feature-based installation**.
+   1. Select the **Active Directory Domain Services** (AD DS) role.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/active-directory-v2/active-directory-v2-add-roles.png')} style={{border:'1px solid gray'}} alt="Add roles" width="600"/>
+   1. Proceed with the installation and wait for it to complete.
+1. Promote the server to a domain controller.
+   1. After installation, navigate to **Server Manager > AD DS**.
+   1. Click on **Promote this server to a domain controller**.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/active-directory-v2/active-directory-v2-promote-server.png')} style={{border:'1px solid gray'}} alt="Promote server" width="600"/>
+   1. Choose **Add a new forest** and provide a root domain name (for example, `csoar.com`).<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/active-directory-v2/active-directory-v2-root-domain-name.png')} style={{border:'1px solid gray'}} alt="Root domain name" width="600"/>
+   1. Configure **Domain Controller Options**.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/active-directory-v2/active-directory-v2-domain-controller-options.png')} style={{border:'1px solid gray'}} alt="Domain controller options" width="600"/>
+   1. Set a **Directory Services Restore Mode (DSRM) password**.
+   1. Complete the installation and restart the server.
+1. Verify Active Directory setup.
+   1. After rebooting, log back in and open **Active Directory Users and Computers**.
+   1. Verify that the domain is properly configured.
+
+## Active Directory V2 in Automation Service and Cloud SOAR
+
+### Required resources from an existing Active Directory installation
+
+To configure the Automation Service or Cloud SOAR to connect to an existing Active Directory installation, enter details about the Active Directory instance in the new resource configuration dialog:
+1. Access integrations in the [Automation Service](/docs/platform-services/automation-service/automation-service-integrations/#view-integrations) or [Cloud SOAR](/docs/cloud-soar/automation).
+1. After the list of the integrations appears, search for the **Active Directory V2** integration and click on the row.
+1. The integration details will appear. Click on the **+** button to add a new resource.
+1. Populate all the required fields (\*), including:
+   * **Host**. The hostname or IP address of the AD server.
+   * **Login Port**. The port used for LDAP authentication (the default is `389` for LDAP and `636` for LDAPS).
+   * **Login DN (Distinguished Name)**. Enter the distinguished name format (for example, `CN=Administrator,CN=Users,DC=csoar,DC=com`). See the following sections for information about how to get the login DN.
+   * **Password**. The corresponding password for the provided username.
+1. Click **SAVE**.
+
+### How to get login DN with a local account
+
+#### Method 1: Using PowerShell (Get-ADUser)
+
+1. Open PowerShell as an administrator.
+1. Run the following command:
+   ```
+   Get-ADUser -Identity Administrator | Select-Object DistinguishedName
+   ```
+1. Example output:
+   ```
+   DistinguishedName
+   -----------------
+   CN=Administrator,CN=Users,DC=csoar,DC=com
+   ```
+
+The `DistinguishedName` field contains the full LDAP path.
+
+#### Method 2: Using Active Directory Users and Computers (GUI)
+
+1. Open **Active Directory Users and Computers (ADUC) (dsa.msc)**.
+1. Enable "Advanced Features" by selecting **View > Advanced Features**.
+1. Navigate to the user account (for example, **Administrator**).
+1. Right-click the user and select **Properties**.
+1. Go to the **Attribute Editor** tab.
+1. Find the `distinguishedName` attribute. The value will be like: `CN=Administrator,CN=Users,DC=csoar,DC=com`. This is your **Login DN**.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/active-directory-v2/active-directory-v2-login-dn.png')} style={{border:'1px solid gray'}} alt="Login DN" width="600"/>
+
+### How to get login DN with a service account
+
+Once the service account is created in the Organization Unit:
+1. Open PowerShell as an administrator.
+1. Run the following command:
+   ```
+   Get-ADUser -Identity <service-account-name>
+   ```
+1. To view all the service accounts inside AD:
+   ```
+   Get-ADUser -Filter * | Select-Object Name, SamAccountName, DistinguishedName
+   ```
+1. Example output:<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/active-directory-v2/active-directory-v2-dn-output-example.png')} style={{border:'1px solid gray'}} alt="DN example output" width="700" height="120"/>
+1. Below is the example path:<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/active-directory-v2/active-directory-v2-example-path.png')} style={{border:'1px solid gray'}} alt="Example path" width="700" height="400"/>
+1. Add the `distinguishedName` as the **Login DN** and correct the password of the service account.<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/active-directory-v2/active-directory-v2-edit-resource.png')} style={{border:'1px solid gray'}} alt="Edit resource" width="400"/><br/>Below is the full form of each term:<br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/active-directory-v2/active-directory-v2-full-form.png')} style={{border:'1px solid gray'}} alt="Full form of terms" width="400"/>
+
 ## Change Log
 
 * March 25, 2021 - First upload