Google Archives - 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

FYI: Next step will be to add support for Google Shared Drives.
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
06 Nov
Url save after file transfer to Google Cloud
Q: Url save after file transfer to Google Cloud possible with Limagito File Mover?
I have a question about how to create URL links from Google Cloud. When files are transferred from local storage to GCloud we need to replace the local file with an URL from Gcloud. Can you help us?
A: In version v2023.0.11.6 we added a new option which makes this possible. This option will create a .url file in the folder where the source file was found (this can be adjusted). The .url file will work as a shortcut to the file the was uploaded to Google Cloud.
We added some screenshots to get you started.
As source we are using a Windows folder [WIN]:
Be sure to exclude *.url filenames because otherwise we would also try to upload the newly created shortcut files (.url) to Google Cloud.
In our destination setup, we are using GCloud as Destination. Information about Google Cloud as destination can be found here.
In the ‘Common’ tab of the GCloud setup you need to enable: ‘Create Shortcut On Success’ which will create the .url file after a successful file transfer to google cloud. The default output path for the shortcut .url file is parameter %SFP which translates as Source File Path.
RunTime log result:
The following .url file was created:
Content of such a .url file:
Information about request endpoints can be found: here
#FileTransfer #googlecloud
If you need any info about this new ‘Url save after file transfer to Google Cloud’ option, please let us know.
Best regards,
Limagito Team
By Limagito-Team Google gcloud, goolge cloud, shortcut, url save
27 Oct
Google Drive migrate from the OAuth out-of-band (OOB) flow
How to migrate from OAuth out-of-band (OOB) flow
Google Out-Of-Band (OOB) flow Migration Guide
Key compliance dates
February 28, 2022 – new OAuth usage blocked for the OOB flow
September 5, 2022 – a user-facing warning message may be displayed to non-compliant OAuth requests
October 3, 2022 – the OOB flow is deprecated for OAuth clients created before February 28, 2022
Please open your Google Drive Setup in Limagito File Mover because we’ll need to make some adjustments.
– We switched to API v3 but should also work with v2. When using API v3 and x64bit, please use a version starting from v2022.10.27.0
– Please add the following information to the OAuth2 setup:
– Authorization Endpoint URL: https://accounts.google.com/o/oauth2/v2/auth
– Token Endpoint URL: https://www.googleapis.com/oauth2/v4/token
– Client ID
– Client Secret
– Scope: https://www.googleapis.com/auth/drive
– Redirect URI: http://127.0.0.1
– Redirect Port: 3017 (can be any other port that is not in use)
Click GET and your browser will open. Please follow the steps in your browser and after acceptance we will automatically fill in Refresh Token and Access Token. Do not forget to <Save> afterwards.
—
#FileTransfer #OAuth
If you need any info about this ‘migrate from OAuth out-of-band (OOB) flow’ How To, please let us know.
Best regards,
Limagito Team
By Limagito-Team Google OAuth2 oauth, OAuth2, OOB, Out-Of-Band