Overview

Integration of SoftNAS Cloud® into Active Directory enables domain users to more securely share files and data in a corporate environment. Authentication is managed by Active Directory (AD) via Kerberos.

...

Please use the following process to integrate AD with SoftNAS Cloud® and Linux with Samba.

Note: SoftNAS does not support single label domains (domains without a suffix such as .com, for example: softnas.domain rather than softnas.domain.com). This warning will typically only apply to clients running servers older than Server 2008 R2.  Windows Server 2008 R2 and up no longer supports the creation of these single label domains. 

Active Directory Wizard

Note: Prior to configuring the Active Directory Wizard, you should make sure that the server IP address is added as Domain name server to Hosts and DNS Clients from Network Settings in the Storage Administration pane. See Hostname and DNS Client for more info.

Configure AD using the Active Directory Wizard. This enables integration automation with AD.

...

1. From Volumes and LUNS, click on Active Directory.
   The AD Wizard instructions are displayed. 
   
   
   
   
   
2. Click on Next.
   
3. Provide the domain name of the active directory domain controller, and then click on Next.
    
   Image Removed
   Enter the active directory NetBIOS Domain. 
   Note: The NetBIOS domain name is required for interoperability with older computers and services.
    Image Removed
   Enter the FQDN of the domain controller. 
   Image Removed
   Provide the AD administrator credentials. 
   Image Removed
   Enable the required groups [pre 3.5].
   Image Removed
   Image Added
4. Provide the Active Directory username in the format domain\user, and the password. Click Next.
   
   Image Added
   
   
   
5. Click on Finish.
   Image Removed
   Image Added
   
   
   

Adding HA pairings to Active Directory

If connecting SoftNAS instances in a High Availability pairing to Active Directory, you must perform the process above twice, once on each node. Active Directory configurations do not carry over to the second node automatically because the target node's NAS services (amongst others) are not running while the node is dormant. Settings cannot be automatically triggered upon takeover. In order for the second instance to remain in Active Directory after a failover the second node must be added as well.

...