Samba File Server Configuration (SMB/CIFS)

Introduction

Myota Vault can connect to Windows file servers, and other SMB-compatible servers (e.g., Samba), by using the SMB/CIFS backend.

Dependencies

All dependencies to connect to an SMB server, except for testing the connection manually, are provided by the Myota Vault image.

Access Testing

The Docker image does not provide the smbclient CLI tool. To mitigate this issue, you need to manually create an image that installs and enables this requirement.

To ensure that you can connect to your file server with SMB, do a small test upfront like the following.

sudo smbclient -L <file_server_name> -U <full_domain_name>/<user_name>

Make sure you have resolved any issues before connecting Myota Vault to an SMB file server.

Configuration

When configuring Myota Vault, you will need the following information:

  • The folder name, which will be your local mount point.

  • The URL of the Samba server.

  • The username or domain/username used to login to the Samba server.

  • The password to login to the Samba server.

  • The share name to mount on the remote Samba server.

  • The remote subfolder inside the remote Samba share to mount.
    This is optional, as it defaults to /.

    To assign the Myota Vault logon username automatically to the subfolder, use $user instead of a subfolder name. The foldername=username must be present and is not created on access.

  • The Myota Vault users and groups who get access to the share.

  • A domain name, might be required or optional depending on your setup

    You can specify a Domain which is useful in cases where the SMB server requires a domain and a username, and an advanced authentication mechanism like Active Directory (AD), or when using session credentials where the username cannot be modified. This is concatenated with the username, so the backend gets domain\username

Further Information