$ 448.33
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Community Apps Dependencies | Show |
| Lines of code | 6218 |
| Technical Name |
attachment_storage_manager_ftps |
| License | OPL-1 |
| Website | https://spre.es/shop/attachment-control-for-odoo-ftps-connector-78 |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Community Apps Dependencies | Show |
| Lines of code | 6218 |
| Technical Name |
attachment_storage_manager_ftps |
| License | OPL-1 |
| Website | https://spre.es/shop/attachment-control-for-odoo-ftps-connector-78 |
| Versions | 17.0 18.0 19.0 |
FTPS connector for Attachment Control
Attachment Control - FTPS
Add FTPS as a storage backend for Attachment Control so routing, audit, move, storage archive and restore workflows can work with FTPS servers through credential-based access.
FTPS
Routing, Move, Storage, Restore
Optional Connector Add-on
Availability: Odoo Online: not recommended | Odoo.sh: generally supported if the FTPS endpoint is reachable | On Premise: supported
Support: info@spre.es
What this connector adds
- FTPS provider in Storage Credentials: create credentials for FTPS servers.
- Credential-based backend usage: the core module can use FTPS in routing, move, storage archive and restore flows.
- Generic backend operations: read, write, delete, list and connection test through the common backend API.
- Provider isolation: FTPS-specific logic stays outside the core module.
Opt-in only: installing this connector does not send data to an FTPS server by itself. External communication only starts after the user creates and validates an FTPS credential and explicitly selects it in the corresponding configuration or workflow.
Data sent only after opt-in: attachment binary content, remote path, and the technical metadata needed by the selected workflow, such as filename, mimetype, file size or checksum when available.
No data is sent to the developer. Data is sent only to the FTPS service explicitly configured by the user.
No data is sent to the developer. Data is sent only to the FTPS service explicitly configured by the user.
Compatibility
- On-premise: supported.
- Odoo.sh: generally supported if the FTPS endpoint is reachable from the runtime environment.
- Odoo Online: not recommended because external endpoint configuration and runtime network behavior may be restricted.
Why a separate add-on? The core module remains provider-agnostic and only this connector knows how to communicate with FTPS endpoints.
Requirements
- Install the core module Attachment Control.
- Install this connector module
attachment_storage_manager_ftps. - Prepare a reachable FTPS endpoint with valid credentials and write permissions.
- Restart Odoo if needed by your deployment process.
Credential fields
Endpoint URL: required FTPS endpoint. It should point to the FTPS server host and optional port.
Container / Bucket: optional top-level folder under the FTPS account.
Path Prefix: optional folder prefix used inside the remote location.
Username and Password: FTPS login credentials.
Extra Parameters (JSON): optional advanced parameters such as timeout or passive mode options if supported by the connector.
Important: FTPS is not the same as SFTP. This connector is for FTPS (FTP over TLS), not SSH/SFTP servers.
How it is used
1. Create an FTPS credential in Storage Credentials.
2. Validate the credential from Odoo.
3. Select that credential in the corresponding routing or storage configuration of the core module.
4. Use audit and move workflows to place attachments on FTPS.
5. Use storage and restore workflows from the core module as usual; this connector only provides the backend integration.
Operational notes
- The remote FTPS path must already exist and be writable before running move, storage or restore operations.
- Always test the credential before enabling production use.
- Verify that the server really supports FTPS and not only plain FTP or SFTP.
- For long-running jobs, configure
limit_time_real_cron = 3600inodoo.conf.
Operational safety
Important: we recommend carrying out all tests beforehand in a test database and making a complete backup before any intervention. We do not assume responsibility for possible incidents, misuse or data loss that may occur during its use.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module