Wiki source code of Gestionnaire de serveurs de fichiers
Last modified by Aurelie Bertrand on 2026/07/16 10:22
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
1.1 | 1 | {{ddtoc/}} |
| 2 | |||
| 3 | (% class="wikigeneratedid" %) | ||
| |
4.1 | 4 | The Server URL manager allows you to manage file servers. |
| 5 | You can add, edit, or delete file servers. | ||
| |
1.1 | 6 | |
| 7 | (% class="wikigeneratedid" %) | ||
| |
4.1 | 8 | [[image:FileServer_manager_en.png]] |
| |
1.1 | 9 | |
| 10 | (% class="box infomessage" %) | ||
| 11 | ((( | ||
| |
4.1 | 12 | ℹ The icon in front of the file server name indicates whether it is valid. |
| |
1.1 | 13 | ))) |
| 14 | |||
| |
4.1 | 15 | = Adding a file server = |
| |
1.1 | 16 | |
| |
4.1 | 17 | To add a new file server: |
| |
1.1 | 18 | |
| |
4.1 | 19 | 1. Click the **+** button, then select the server type from the displayed list. |
| 20 | ➡ The **Add a file server** box appears with the selected type. | ||
| 21 | [[image:FileServer_manager_add_en.png]] | ||
| 22 | 1. Select the server **Type** from the drop-down list. | ||
| 23 | 1. Enter the **Server name**. | ||
| 24 | 1. In the **URL field**, enter the server address. This address depends on the server type used. For example: | ||
| 25 | 1*. Samba: smb:~/~/192.168.1.1/documents | ||
| 26 | 1*. FTP: 192.168.1.1 | ||
| 27 | 1*. File System: c:/documents | ||
| 28 | 1*. WebDav: [[__http:~~/~~/192.168.1.1/webdav/www__>>url:http://192.168.1.1/webdav/www]] | ||
| 29 | 1. Fill in the **File path**. For example: | ||
| 30 | 1*. **/.* **retrieves all documents | ||
| 31 | 1*. **doc/.* **retrieves documents in the doc directory | ||
| 32 | 1*. **${user.uid}/.*** retrieves documents in the ${user.uid} directory | ||
| 33 | 1. Check the **Explore subfolders** box if you want to be able to search for files in subfolders. | ||
| 34 | Enter the **Subfolder level** to which you want to limit the exploration. | ||
| 35 | 1. Check the **Read-only** box if you want this server to be usable in read-only mode. Users will not be able to add or update documents on this server. | ||
| 36 | 1. If the file server is not restricted to a role (field **Role**), you can check the **Public** box if you want to allow a user without the //Studio > Manage common elements// permission to add, overwrite, or delete a document there. See the Public server section below for more details. | ||
| 37 | 1. Enter the **Username** and **Password** used to connect to the document server (optional). | ||
| 38 | 1. In the **Role** field, select the role to which you want to restrict full access to the server, or **None** to allow full access for all roles. The field can also be used as a search bar in case of a large number of roles. | ||
| 39 | 1. To the right of **Share**, click **Select alloewed roles** if you want to restrict the server's visibility to certain roles. | ||
| 40 | 1. For certain server types, additional configuration parameters must be filled in:((( | ||
| 41 | |=(% scope="row" style="width: 160px;" %)Server type|=(% style="width: 242px;" %)Parameter|=(% style="width: 504px;" %)Description | ||
| 42 | |=(% style="width: 160px;" %)Samba|(% style="width:242px" %)Access via SMB2/SMB3 protocol|(% style="width:504px" %)SMB1 is the default supported protocol. Check the box to use the SMB2/SMB3 protocol. | ||
| |
1.1 | 43 | |=(% style="width: 160px;" %)((( |
| 44 | FTP | ||
| 45 | |||
| 46 | |||
| 47 | FTPS | ||
| 48 | )))|(% style="width:242px" %)Port | ||
| |
4.1 | 49 | FTP mode |
| 50 | \\Encryption|(% style="width:504px" %)((( | ||
| 51 | See the [[FTP(S) Document Server>>doc:Digdash.deployment.Document_managers.ftps.WebHome]] page for a detailed description. | ||
| |
1.1 | 52 | ))) |
| |
4.1 | 53 | |=(% style="width: 160px;" %)SFTP|(% style="width:242px" %)Port|(% style="width:504px" %)Enter the port number. |
| |
1.1 | 54 | |=(% style="width: 160px;" %)Google Drive|(% style="width:242px" %)((( |
| |
4.1 | 55 | Service account |
| 56 | P12 file | ||
| 57 | Shared with | ||
| 58 | Convert to Google format | ||
| 59 | )))|(% style="width:504px" %)See the [[Google Drive settings configuration>>doc:Digdash.deployment.Document_managers.google_drive.WebHome||anchor="Parametres_Drive"]] paragraph for a detailed description. | ||
| 60 | |=(% style="width: 160px;" %)HDFS|(% style="width:242px" %)CSRF prevention header|(% style="width:504px" %)If CSRF protection is enabled in the HDFS configuration, specify the header. | ||
| 61 | Only compatible with HADOOP 2.8.0 and above. | ||
| |
1.1 | 62 | ))) |
| |
4.1 | 63 | 1. You can finally click the **Test connection** button. |
| |
1.1 | 64 | |
| 65 | (% class="box warningmessage" %) | ||
| 66 | ((( | ||
| |
4.1 | 67 | ❗The document server identifier, used to uniquely identify it, can also be edited. |
| 68 | However, it should only be modified in specific situations, notably to simplify migrating from a development environment to a production environment (see documentation [[Backup and restore>>doc:Digdash.deployment.configuration.backup_restore.WebHome]]). | ||
| |
1.1 | 69 | ))) |
| 70 | |||
| |
4.1 | 71 | == Public server{{id name="Public"/}} == |
| |
1.1 | 72 | |
| |
4.1 | 73 | Checking the **Public** box allows a user with the **Data model designer** permission group to add, overwrite, or delete a document on a file server not restricted to a role. |
| 74 | The **Public** option is enabled by default on the first server startup (after installation) for the "Common datasources" and "User docs" file servers. If you make these servers non-public, they will remain non-public after an update or restart. | ||
| 75 | The option is disabled by default for other existing servers. | ||
| 76 | The option is disabled by default for a newly created file server as well as file servers restricted to a role. | ||
| |
1.1 | 77 | |
| |
4.1 | 78 | The table below summarizes the capabilities of a user with the **Data model designer** permission group. |
| |
1.1 | 79 | |
| |
4.1 | 80 | |=(% style="width: 428px;" %)Action |=(% style="width: 429px;" %)WITHOUT the "Studio > Manage common items" permission |=(% style="width: 435px;" %)WITH the "Studio > Manage common items" permission |
| 81 | |(% style="width:428px" %)Access to managers (files and servers)|(% style="width:429px" %)✅ Yes|(% style="width:435px" %)✅ Yes | ||
| 82 | |(% style="width:428px" %)Adding / deleting / renaming / uploading files on a public server|(% style="width:429px" %)✅ Yes|(% style="width:435px" %)✅ Yes | ||
| 83 | |(% style="width:428px" %)Downloading from a non-public server|(% style="width:429px" %)✅ Yes|(% style="width:435px" %)✅ Yes | ||
| 84 | |(% style="width:428px" %)Adding / deleting / modifying files on a non-public server|(% style="width:429px" %)❌ No|(% style="width:435px" %)✅ Yes | ||
| 85 | |(% style="width:428px" %)Creating a server|(% style="width:429px" %)✅ Yes, but only for its roles (Public box unchecked and grayed out)|(% style="width:435px" %)✅ Yes, without restriction | ||
| 86 | |(% style="width:428px" %)Duplicating / editing / deleting a server|(% style="width:429px" %)✅ Yes, but only for a role-restricted server for which it has write rights|(% style="width:435px" %)✅ Yes (all servers) | ||
| |
1.1 | 87 | |
| |
4.1 | 88 | == Authentication for an HDFS server {{id name="HDFS"/}} == |
| |
1.1 | 89 | |
| |
4.1 | 90 | In the general case, unsecured authentication is used to connect to an HDFS server. |
| 91 | Only the username needs to be specified in the connection configuration (no password). | ||
| 92 | The username parameter is sent in HTTP requests. | ||
| |
1.1 | 93 | |
| |
4.1 | 94 | If Apache Sentry (or an authentication proxy) is used to authenticate with HDFS, a basic authentication mechanism is used. |
| 95 | The username and password must then be specified in the connection configuration. | ||
| 96 | The username and password are sent in an HTTP header. | ||
| |
1.1 | 97 | |
| |
4.1 | 98 | = Duplicating / Editing / Deleting a file server = |
| |
1.1 | 99 | |
| |
4.1 | 100 | You can also: |
| |
1.1 | 101 | |
| |
4.1 | 102 | * Duplicate a file server: select the original server, click the [[image:en_Duplicate_button.png||alt="Duplicate" height="20" width="22"]] button, and modify the settings as desired. |
| 103 | * Edit a file server: select the server to modify, click the [[image:en_Edit_button.png||alt="Edit" height="20" width="21"]] button, and modify the settings as desired. | ||
| 104 | * Delete a file server: select the server to delete and click the [[image:en_Delete_button.png||alt="Delete" height="20" width="20"]]. | ||
| |
1.1 | 105 | |
| 106 | (% class="box infomessage" %) | ||
| 107 | ((( | ||
| |
4.1 | 108 | You can also access these functions as well as the [[dependency analysis tool>>doc:Digdash.user_guide.studio.managers.dependencies.WebHome]] by right-clicking on a server in the list. The dependency analysis tool allows you to check dependencies on the server. |
| 109 | [[image:FileServer_manager_context_menu_en.png]] | ||
| |
1.1 | 110 | ))) |