Help Center/ Scalable File Service/ User Guide/ SFS Turbo File Systems/ File System Permissions Management
Updated on 2024-07-29 GMT+08:00
View PDF

File System Permissions Management

Overview

You can add permissions rules to grant different permissions to different clients.

There is a default rule (*, rw, no_root_squash), which grants all client users with read/write permissions to access the file system and does not change the root user to an unprivileged account. You can delete this rule if needed.

Considerations

  • A maximum of 64 permissions rules can be added for a file system.
  • Permissions rules can be added or deleted, but there should be at least one permissions rule for a file system.
  • File system permissions can only be managed via APIs currently. For details, see Scalable File Service API Reference

IP Address Ranges

You can configure authorized IP address ranges in either of the following ways:

  • *: means any IP address.
  • CIDR blocks:

    A CIDR block uses a variable-length subnet mask to show the ratio of the network bits to host address bits within a range of IP addresses.

    A suffix value is added at the end of an IP address to form a CIDR block. This suffix shows the bits of the network address. For example, 192.1.1.0/24 is an IPv4 CIDR block, in which the first 24 bits (192.1.1) are the network address.

    Any IP address whose first 24 bits are the same as those of 192.1.1.0 will be applied with this permissions rule. In other words, 192.1.1.1 and 192.1.1.1/32 have the same effect.

Types of Permissions

There are access permissions and squash permissions.

Table 1 Access permissions

Permissions

Description

rw

Users have the read/write permissions.

ro

Users have the read-only permissions.

none

Users have no permissions to access the file system.
Table 2 Squash permissions

Permissions

Description

all_squash

All users access the file system as the nobody user.

root_squash

The root user accesses the file system as the nobody user.

no_root_squash

All users (including the root user) who access the file system will not mapped to the nobody user.

If an IP address is matched with two permissions rules, the more accurate rule will be applied. For example, if 1.1.1.1 is matched with both permissions rules (1.1.1.1, ro, root_squash) and (*, rw, no_root_squash), the more accurate rule (1.1.1.1, ro, root_squash) will be applied.

Parent topic: SFS Turbo File Systems