Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Integration of SoftNAS® 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® 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. 

Prerequisites:

  • A DNS Server must be configured
  • An existing Active Directory set-up and running
  • Prior to configuring the Active Directory Wizard, you must add the server IP address as Domain name server within the Hosts and DNS Clients applet, found in Network Settings in the Storage Administration pane. See Hostname and DNS Client documentation for more info.

Active Directory Wizard

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 (FQDN)  and NetBIOS (host) name of the active directory domain controller.
     


  4. Provide the Active Directory username in the format domain\user, and the password. Click Next.




  5. Click on Finish.




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.

...