File Permission Configuration in Linux

Below are potential issues caused by missing file permissions categorized by folder path:

webroot/help: Lacking permission on the help folder generally has no impact. However, without the permission on the FRDemo.db file within, you cannot preview built-in templates in the designer.

webroot/logs/cubes: Tracking data cannot be collected, and Swift queries or data writes will fail.

WEB-INF/assets/scripts: The Plugin Management module cannot be displayed.

WEB-INF/assets: Chart resources cannot be read (chartmapsvg, map); solid files cannot be generated (clouds); templates using the new engine cannot be previewed (engine); the cache cannot be read or written (temp_attach); backup templates cannot be created (vcs).

WEB-INF/assist: The cloud O&M data package cannot be downloaded (clouds), and the built-in plugins cannot be updated (update).

WEB-INF/classes: Custom class files cannot be called.

WEB-INF/config: Since the configuration files within cannot be read, relevant configurations, including migration, cluster, and logs, will not take effect.

WEB-INF/embed: If the built-in FineDB is used as the configuration database, FineDB cannot be read, causing FineReport startup failure.

WEB-INF/lib: FineReport cannot be started.

WEB-INF/plugins: Plugins fail to load and therefore cannot be used.

WEB-INF/reportlets: Template files cannot be read.

WEB-INF/resources: Local registration via the lic file fails.

WEB-INF/schedule: Result files of scheduled tasks fail to be generated.

Note: 

For proper operation of the project, ensure that at least the 755 permission on project folders is granted.

File Permission Check

1. Command

ls -l: The command is used to view the permissions of all files and folders in the current directory.

ls -l xxx: The command is used to view the permissions of a specified file (xxx) or files within a specified directory (xxx).

2. Permission description

Take the drwxr-xr-x permission, represented using ten characters, as an example.

The 1st character (d in this example) represents the file type, with d standing for a directory and a hyphen (-) for a regular file.

The 2nd to 4th characters (rwx in this example) represent the permissions assigned to the owners of the file.

The 5th to 7th characters (r-x in this example) represent the permissions assigned to the groups.

The 8th to 10th characters (r-x in this example) represent the permissions assigned to others.

r stands for read, indicating that the file can be read.

w stands for write, indicating that the file can be modified or deleted.

x stands for execute, indicating that executable files (for example, a program) can be run.

- indicates that no permission has been granted.

In the figure above, root root represents the owner and owning group of the file or directory.

3. Example

The drwxr-xr-x (or 755, the corresponding octal value) permission indicates the permissions on the directory: The root user (owner of the file) has the read, write, and execute permissions; the root group has the read and execute permissions; and all other users, who are neither the root user nor in the root group, have read and execute permissions.

The -rw-r--r-- (644) permission indicates the permissions on the file: The root user (owner of the file) has read and write permissions; the root group has the read permission; and all other users have the read permission.

Modifying the Permission

Command

1. To assign the write permission on the file xxx.xxx to others, you can use the command:

chmod o+w xxx.xxx

2. To remove the read and write permissions from the file xxx.xxx for groups and others, you can use the command:

chmod go-rw xxx.xxx

Detailed Description

u stands for the user owner.

g stands for the group to which the owner belongs.

o stands for others, excluding the user owner and owning group.

a stands for all, including the owner, owning group, and others.

r stands for read, indicating that the file can be read.

w stands for write, indicating that the file can be modified or deleted.

x stands for execute, indicating that executable files (for example, a program) can be run.

You can also use octal numbers to represent Linux file permissions.

r ------------4

w -----------2

x ------------1

- ------------0

Operation:

Plus sign (+): adding the permissions

Minus sign (-) : removing the permission

Equal sign (=): Replacing the existing permissions with the new permissions you specify

Some of the frequently used permissions are explained as follows:

-rw------- (600): read and write permissions for the owner only

-rw-r--r-- (644): read and write permissions for the owner, and read permission for groups and others

-rwx------ (700): read, write, and execute permissions for the owner only

-rwxr-xr-x (755): read, write, and execute permissions for the owner, and read and execute permissions for groups and others

-rwx--x--x (711): read, write, and execute permissions for the owner, and the execute permission for groups and others

-rw-rw-rw- (666): read and write permissions for all

-rwxrwxrwx (777): read, write, and execute permissions for all