2024 - Page 9 of 19 - File transfer tool from Limagito

23 Jul
How to access Google Drive using a JSON or PKCS12 Private Key
How to access Google Drive using a JSON or PKCS12 Private Key
In version v2024.7.23.0 we add the following Google Drive options:
Access using a JSON Private Key file
Access using a .p12 Private Key file
Delegated Access option
In your Google Drive setup:
API must be Vendor 2 – CK
Auth Type > Private Key File (JSON or .12)
Switch to Security Tab:
Select the “Key” button to import the Private Key File
The content of the file is imported to our settings database (AES256 encrypted)
On this Security Tab you can enable Delegated Access
Select the Private Key file you want to use. We downloaded these files from the Google Cloud Console after adding a service account.
Google Cloud Console ‘Service Accounts’ setup:
Double click on your Service Account and switch to KEYS tab:
Result:
Delegated Access:
To use delegated access you’ll need to:
Add the email address of your service account to the ‘Email Address field’
not needed with JSON because this address is in the JSON file
Add the email address of the user for which the application is requesting delegated access to the ‘Sub Email Address’ field.
Enable domain-wide authority to the service account: link
If you need any help with this ‘JSON or PKCS12 Private Key’ option, please let us know.
Best Regards,
Limagito Team
#managedfiletransfer #filetransfer #filemanagement
By Limagito-Team Google .p12, delegated, PKCS12
20 Jul
How to halt moving too many files and send an alert
How to halt moving too many files and send an alert
Q: I have a job that moves files from an external S3 bucket into our local storage. The other day a vendor hiccupped and sent 8000 files. Limagito did it’s job and moved them over, which ended up gumming up our systems. Is there any way to limit transfers? I’ve been looking through Help and haven’t seen anything yet.
For instance…I know this vendor normally sends around 10 a month. Anything over 50 would obviously be abnormal and It would be great to throttle them, even better to send an alert and let us know, so we can correct the issue.
Any help would be greatly appreciated.
A: Please have a look at the following setup. So we’ll allow only a maximum of files per month.
We used a Windows folder as Source:
– Function Setup > set Destination Options to ‘Destination Memory & Exit Cyclus on Error’
– Destination Setup:
First Destination: Pascal Script
This script will check the month and the amount of files it successfully moved
You can adjust the “ctMaxFilesAllowed” Const value to allow more or less files per month
Second Destination: your output, can be any Destination type.
Third Destination: Pascal Script
Will increase the internal counter (VIA) if a file is successfully moved
Link to both scripts, for the first and third Destination.
First Destination (Pascal Script):
Third Destination (Pascal Script):
– Open Our Rule Events option:
– Select and enable ‘On Pascal Script Error’ event. Enable ‘Enable Mail’ and adjust the mail setup. There is a test button available.
Enable the ‘Error event memory’ because otherwise you’ll get too many emails in case the maximum of files is reached.
FYI: When you would test this setup and max files are reached we added a way to reset the internal counter (max files allowed per month).
Right click on the Counter value below and select ‘Reset Counter’.
This is is just an example of what is possible. If you need any help with this ‘halt moving too many files’ setup, please let us know.
Best Regards,
Limagito Team
#managedfiletransfer #filetransfer #filemanagement
By Limagito-Team Events How-to Pascal Script halt moving, too many files
14 Jul
SFTP Allowed Algorithms in Limagito File Mover
SFTP Set Allowed Algorithms in Limagito File Mover
14th of July 2024
By default, Limagito File Mover orders algorithms according to best practices, and pays attention to vulnerabilities such as the “Terrapin Attack”.
The following algorithms are supported by Limagito File Mover when our second API Vendor – CK is selected:
Hostkey:
ssh-ed25519
rsa-sha2-256
rsa-sha2-512
ecdsa-sha2-nistp256
ecdsa-sha2-nistp384
ecdsa-sha2-nistp521
ssh-rsa
ssh-dss
Key Exchange:
curve25519-sha256
curve25519-sha256@libssh.org
ecdh-sha2-nistp256
ecdh-sha2-nistp384
ecdh-sha2-nistp521
diffie-hellman-group14-sha256
diffie-hellman-group1-sha1
diffie-hellman-group14-sha1
diffie-hellman-group16-sha512
diffie-hellman-group18-sha512
diffie-hellman-group-exchange-sha256
diffie-hellman-group-exchange-sha1
Ciphers:
aes128-ctr
aes256-ctr
aes192-ctr
aes128-cbc
aes256-cbc
aes192-cbc
aes128-gcm@openssh.com
aes256-gcm@openssh.com
twofish256-cbc
twofish128-cbc
blowfish-cbc
(also chacha20-poly1305@openssh.com if explicitly allowed by the application)
MAC Algorithms:
hmac-sha2-256
hmac-sha2-512
hmac-sha1
hmac-ripemd160
hmac-sha1-96
hmac-md5
(also the following etm algorithms if explicitly allowed)
hmac-sha1-etm@openssh.com
hmac-sha2-256-etm@openssh.com
hmac-sha2-512-etm@openssh.com

Best Regards,
Limagito Team
#SFTP #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team SFTP Algorithms