Skip to content

Active Directory & Kerberos

Integrate MayaNAS with directory services for centralized authentication. Required for Kerberos-secured NFS exports and domain-joined SMB sharing.

Navigate to Configure Server > Directory Services in the Web UI sidebar.

ServiceUse Case
Azure Active DirectoryAzure-hosted AD for cloud deployments
FreeIPAOpen-source identity management (Linux-native)
LDAPLightweight Directory Access Protocol
NISNetwork Information Service (legacy Unix)
Kerberos (Standalone)Kerberos KDC without full AD integration
  • AD domain controller reachable from MayaNAS
  • DNS configured to resolve the AD domain
  • An AD account with domain join privileges
  1. Navigate to Configure Server > Directory Services > Active Directory
  2. Click Join
  3. Fill in:
FieldDescription
DomainAD domain name (e.g., corp.example.com)
UsernameAdmin username with join privileges
PasswordAdmin password
Enable WinbindEnable Winbind service for name resolution
  1. Optionally expand Additional Options:
FieldDescription
Computer OUOrganizational Unit for the computer account
User PrincipalUser principal name
Automatic ID MappingMap Windows SIDs to Unix UIDs/GIDs automatically
  1. Click Join

Before joining, you can click Discover to verify DNS resolution and locate domain controllers:

  1. Enter the domain name
  2. Click Discover
  3. Review the discovered domain controllers and services
  1. Click Leave
  2. Confirm the action

Once joined, the configuration panel shows:

  • Domain Name
  • Directory Type
  • Client Software
  • Login Formats
  • Login Policy
  • NFS SPN (Service Principal Name for Kerberos NFS)
  1. Navigate to Configure Server > Directory Services > FreeIPA
  2. Click Join
  3. Fill in:
FieldDescription
DomainFreeIPA domain
UsernameAdmin username
PasswordAdmin password
  1. Optionally configure Computer OU, User Principal, and Automatic ID Mapping
  2. Click Join

Click Leave to disjoin from the FreeIPA domain.

  1. Navigate to Configure Server > Directory Services > NIS
  2. Click Enable
  3. The panel shows the NIS Domain and NIS Server (from ypwhich)

Click Disable to stop NIS name resolution.

For environments with a Kerberos KDC but no full AD or FreeIPA deployment.

  1. Navigate to Configure Server > Directory Services > Kerberos
  2. Fill in:
FieldDescriptionDefault
RealmKerberos realm (e.g., CORP.EXAMPLE.COM)
KDC ServerHostname or IP of the KDC
KDC PortKDC port88
  1. Click Save

Click Test to verify connectivity to the KDC.

A keytab file is required for NFS Kerberos. The keytab must contain an nfs/<hostname>@REALM principal.

  1. Generate the keytab on the KDC:
    Terminal window
    kadmin -q "ktadd -k nfs.keytab nfs/mayanas.corp.com@CORP.EXAMPLE.COM"
  2. Click Upload Keytab
  3. Select the .keytab file
  4. The panel shows the imported principals

After configuring directory services, NFS shares can use Kerberos security:

  • sec=krb5 — Authentication only
  • sec=krb5i — Authentication + integrity
  • sec=krb5p — Authentication + integrity + encryption

The NFS Shares panel shows a lock icon on Kerberos-secured exports. See NFS Shares for export configuration.

After AD join, SMB shares authenticate domain users automatically:

  • Domain users can access shares with their AD credentials
  • Windows ACLs can be applied via the Security panel
  • Domain-joined clients get transparent Kerberos SSO

See SMB Shares for share configuration.