Connector - Overview
Before setting up import or export jobs in DJUST, you must configure a Connector to securely communicate with your external systems—via FTP or REST API.
This is a requirement to configure a Job to import or export data.
Exception for internal jobsJobs of type Indexation and Order Validation do not require a Connector, as they operate entirely within DJUST and do not communicate with external systems. The
clientConfigurationIdfield is optional for these job types.
🌐 Connector Description
A Connector allows you to:
- Set up authentication credentials (e.g., FTP login/password, API OAuth tokens)
- Define technical parameters (e.g., base URL, port, headers, access token URLs)
- Reuse this configuration across multiple jobs (no need to re-enter credentials for each new job)
One Connector for multiple jobsEach Connector is created once and can be linked to multiple import or export jobs, making job setup faster and more consistent.
🔐 Supported Authentication Methods
Depending on the selected connection type (FTP or API), DJUST supports the following authentication methods:
Connection Type | Supported Methods |
|---|---|
FTP | FTPs (with TLS) SFTP (password-based only) 🚫 SSH key not supported |
API (REST) | No authentication OAuth 2.0 – Password Grant OAuth 2.0 – Client Credentials Grant |
⚙️ Connection Parameters
| Connection Type | Parameters |
|---|---|
| FTP / SFTP | Hostname, Port, Username, Password |
| API (REST) | Base URL, HTTP headers, Access Token URL, Grant type, Client ID, Client Secret, Username, Password |
Updated about 16 hours ago
