Overview
Parameters:FTPUSER
Category: Custom
Default value: String.Empty
Product: eTASK.Other (Custom)
What does this parameter do?
FTPUSER stores the username for authentication on FTP servers. This parameter is used during automated file import to establish a connection to the FTP server and transfer files. The value is automatically stripped of spaces.
What is this parameter used for?
Authentication with FTP servers for automated file import
Transferring files between the eTASK system and external systems
Integration with third-party systems via the FTP protocol
Providing login credentials for FTP connections when no specific login information is stored
Technical Details (for Administrators)
Format: Text string (username)
Default value: String.Empty (empty)
Valid values:
Any valid FTP username
Empty (
String.Empty) if no FTP access is required
Important notes:
The username is automatically stripped of leading and trailing spaces
Used as a fallback credential if no specific login credentials are stored in the database
Serves as the default authentication for FTP connections in the file import module
The parameter is stored unencrypted in the database
Interaction with other parameters:
FTPPASSWORD: The corresponding password for FTP authentication (stored in encrypted form)
FTPSSLENABLED: Controls whether the FTP connection uses SSL/TLS encryption
When should you change this value?
Set the value (enter the username) if:
You want to set up an automated file import via FTP
New FTP credentials have been provided for an external server
The existing FTP credentials have been changed
Centralized FTP authentication is to be used for all import operations
Leave the value blank (String.Empty) if:
No FTP import is used
Individual login credentials are stored in the database for each import operation
Other transfer protocols (e.g., HTTP, local file paths) are used
Important Notes
Fallback Function
This parameter serves as a fallback credential if no specific login credentials are stored during a file import. Individual login credentials take precedence.Encryption
The username is stored unencrypted. The corresponding password (FTPPASSWORD), however, is stored encrypted in the database.Automatic cleaning
Leading and trailing spaces are automatically removed to prevent errors caused by accidental spaces.Security
Use dedicated FTP accounts with minimal permissions. Avoid using administrator or root accounts.
Security
Does changing this parameter affect security?
Yes, the parameter is part of FTP authentication and has a direct impact on the security of data transmission.
Positive aspects:
* Enables controlled authentication on FTP servers
* Allows the use of dedicated service accounts with restricted permissions
* Supports encrypted connections when combined with FTPSSLENABLED
Note:
* The username is stored unencrypted in
the database * Should only be accessible to authorized
administrators * If the username and password are compromised, unauthorized access to the FTP server may occur
* Regular review and updating of access credentials is recommended
Data protection assessment:
- The username itself generally does not contain any personal data
- Access to this parameter should be logged
- Changes should be documented in a traceable manner
Recommendation: Use dedicated FTP service accounts with minimal permissions (read/write access only to the required directories). Enable FTPSSLENABLED for encrypted connections and change the access credentials regularly.
Practical example
Initial situation: Your company receives invoice data daily from an external service provider via an FTP server. The file import is configured, but no FTP credentials have been entered yet.
Configuration: - FTPUSER = "etask_import" - FTPPASSWORD = (encrypted password) - FTPSSLENABLED = 1
After the change:
The system automatically connects to the FTP server using the username "etask_import"
The connection is encrypted via SSL/TLS (FTPSSLENABLED = 1)
Invoice files are automatically downloaded and imported
The import process runs without manual entry of login credentials
Result: The automated file import works reliably and securely. Invoice data is imported daily without requiring manual intervention.
Alternative scenarios:
Scenario A - Multiple FTP servers:
Store individual login credentials for each import process in the database (table GL_ANMELDUNG_T)
FTPUSER remains empty or serves as a fallback for unconfigured imports
Scenario B - Security rotation:
Update FTPUSER and FTPPASSWORD during scheduled credential rotations
Test the new login credentials before going live
Document the change in change management
Recommended setting
For standard installations:String.Empty(empty, no FTP access configured)
Reason:
FTP import is not required in every installation
Access credentials should only be stored if actually needed
Minimizes potential security risks posed by unused credentials
Exceptions (FTP import required):
Set FTPUSER to a dedicated service account name
Configure FTPPASSWORD with the corresponding encrypted password
Enable FTPSSLENABLED for encrypted connections
note2777cd8f-c837-43fb-a5b2-f3cccb71a351
Tip: Use descriptive usernames such as "etask_import" or "service_fileimport" to make mapping and management easier.
Tip: Use descriptive usernames such as "etask_import" or "service_fileimport" to make mapping and management easier.
Tip: Use descriptive usernames such as "etask_import" or "service_fileimport" to make mapping and management easier.