View Attach (16) Info

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
png
 allow_form.png 132.3 kB 2 13-May-2025 04:28 krivacsz
png
 client_id_secret.png 96.8 kB 3 15-May-2025 07:06 krivacsz
png
 consent_settings_1.png 128.9 kB 1 05-Dec-2023 05:32 krivacsz
png
 consent_settings_2.png 42.5 kB 1 05-Dec-2023 05:32 krivacsz
png
 create_consent.png 108.6 kB 1 05-Dec-2023 05:32 krivacsz
png
 create_credentials.png 181.1 kB 2 05-Dec-2023 05:32 krivacsz
png
 create_project.png 25.9 kB 1 05-Dec-2023 05:32 krivacsz
png
 credential_config.png 160.4 kB 4 06-Jun-2025 05:27 krivacsz
png
 credential_config_gdrive.png 166.7 kB 2 06-Jun-2025 07:36 krivacsz
png
 g_api_services.png 95.9 kB 1 13-May-2025 01:59 krivacsz
png
 gmail_api_enabled.png 42.1 kB 1 23-Apr-2025 10:00 krivacsz
png
 not_verified_domain.png 111.6 kB 1 05-Dec-2023 05:32 krivacsz
png
 oauth_consent.png 49.1 kB 1 05-Dec-2023 05:32 krivacsz
png
 oauth_form.png 61.3 kB 1 05-Dec-2023 05:32 krivacsz
png
 pop_imap_task.png 134.8 kB 1 14-May-2025 02:22 krivacsz
png
 smtp_config.png 50.7 kB 2 13-May-2025 04:54 krivacsz

This page (revision-146) was last changed on 06-Jun-2025 07:49 by krivacsz

This page was created on 05-Dec-2023 05:32 by krivacsz

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 3 added one line
----
At line 6 added 2 lines
__⚠️ Constraints__: __It is only supported for accounts with 2-Step Verification enabled.__\\
\\
At line 6 changed one line
__⚠️ Note__: Google strongly recommends using OAuth 2.0 for authentication instead of App Passwords. App Passwords are __only supported for accounts with 2-Step Verification enabled__, and Google is gradually phasing them out in favor of more secure OAuth-based access. Some access types (e.g., less secure apps) are already blocked unless explicitly allowed.\\
__⚠️ Note__: Google strongly recommends using OAuth 2.0 for authentication instead of App Passwords. Some access types (e.g., less secure apps) are already blocked unless explicitly allowed.\\
At line 23 added one line
-----
At line 27 changed one line
__⚠️ Note:__ Ensure sure the __GMAIL API__ is enabled at __Enabled APIs & services__. [Google API Library Link|https://console.cloud.google.com/apis/library]\\
__⚠️ Important:__ Ensure sure the __GMAIL API__ is enabled at __Enabled APIs & services__. [Google API Library Link|https://console.cloud.google.com/apis/library]\\
At line 37 changed 2 lines
Select the application type: __Web application__. Provide a unique name. Then, configure the __Authorized redirect URI__—this is where Google will redirect you after authorization.\\
The __Redirect URL__ must end with __?command=register_google_mail_api__.\\
• Select the application type: __Web application__.\\
• Provide a unique name to identify your OAuth client (e.g., CrushFTP Integration).\\
Then configure the following:\\
• __Authorized JavaScript origins__: Add the base URL of your CrushFTP server (e.g., https://your-domain.com).\\
• __Authorized redirect URIs__: This is the URL Google will redirect to after successful authorization. The Redirect URL must end with: __?command=register_google_mail_api__\\
At line 41 changed 4 lines
http://127.0.0.1:9090/?command=register_google_mail_api
or
https://your.crushftp.domain.com/?command=register_google_mail_api
http://127.0.0.1:9090/?command=register_google_mail_api
or
https://your.crushftp.domain.com/?command=register_google_mail_api
At line 64 added one line
__Important__: After configuration, don’t forget to click __Publish App__ at __Audience__ page to make it active. Without publishing, the app will remain in __Testing__ mode, which restricts access to authorized test users only.\\
At line 78 added one line
----
At line 84 added one line
----
At line 77 changed one line
__⚠️ Note__: To obtain the __Refresh Token__, the CrushFTP WebInterface’s host and port must match the __Redirect URL__ specified in the __Google APIs & Services__-> __Credentials__ -> __OAuth 2.0 Client IDs__. In our example, it was: http://127.0.0.1:9090 or https://your.crushftp.domain.com/\\
__⚠️ Important__: To obtain the __Refresh Token__, the CrushFTP WebInterface’s host and port must match the __Redirect URL__ specified in the __Google APIs & Services__-> __Credentials__ -> __OAuth 2.0 Client IDs__. In our example, it was: http://127.0.0.1:9090 or https://your.crushftp.domain.com/\\
At line 80 changed one line
__⚠️ Note__: Be sure to sign in with the __Google Account__ that has the __necessary permissions__, as configured in the __Google APIs & Services__-> __Credentials__ -> __OAuth 2.0 Client IDs__. This will automatically configure the __SMTP Server Username__ and __SMTP Server Password__.\\
__⚠️ Important__: Be sure to sign in with the __Google Account__ that has the __necessary permissions__, as configured in the __Google APIs & Services__-> __Credentials__ -> __OAuth 2.0 Client IDs__. This will automatically configure the __SMTP Server Username__ and __SMTP Server Password__.\\
At line 113 changed one line
__a.)__ App passwords: [1. Google App Passwords Link|https://www.crushftp.com/crush11wiki/Wiki.jsp?page=SMTP%20Google%20Mail%20Integration#section-SMTP+Google+Mail+Integration-1.GoogleAppPasswords]\\
----
__a.)__ App passwords: ⚠️ Constraints: It is only supported for accounts with 2-Step Verification enabled.
[1. Google App Passwords Link|https://www.crushftp.com/crush11wiki/Wiki.jsp?page=SMTP%20Google%20Mail%20Integration#section-SMTP+Google+Mail+Integration-1.GoogleAppPasswords]\\
At line 129 added one line
----
At line 119 changed one line
__⚠️ Note__: To obtain the Refresh Token, the CrushFTP WebInterface’s host and port must match the __Redirect URL__ specified in the __Google APIs & Services__-> __Credentials__ -> __OAuth 2.0 Client IDs__. In our example, it was: http://127.0.0.1:9090 or https://your.crushftp.domain.com/\\
__⚠️ Important__: To obtain the Refresh Token, the CrushFTP WebInterface’s host and port must match the __Redirect URL__ specified in the __Google APIs & Services__-> __Credentials__ -> __OAuth 2.0 Client IDs__. In our example, it was: http://127.0.0.1:9090 or https://your.crushftp.domain.com/\\
At line 122 changed one line
__⚠️ Note__: Be sure to sign in with the __Google Account__ that has the __necessary permissions__, as configured in the __Google APIs & Services__-> __Credentials__ -> __OAuth 2.0 Client IDs__. This will automatically configure the PopImapTask's __Mail Username__ and __Mail Password__.\\
__⚠️ Important__: Be sure to sign in with the __Google Account__ that has the __necessary permissions__, as configured in the __Google APIs & Services__-> __Credentials__ -> __OAuth 2.0 Client IDs__. This will automatically configure the PopImapTask's __Mail Username__ and __Mail Password__.\\
At line 134 changed one line
__⚠️ Note:__ Since the email address is required after obtaining the refresh token, the Mail Username field must be adjusted.\\
__⚠️ Important:__ Since the email address is required after obtaining the refresh token, the Mail Username field must be adjusted.\\
Version Date Modified Size Author Changes ... Change note
146 06-Jun-2025 07:49 8.985 kB krivacsz to previous
145 06-Jun-2025 07:40 8.753 kB krivacsz to previous | to last
144 06-Jun-2025 07:38 8.742 kB krivacsz to previous | to last
143 06-Jun-2025 05:34 8.753 kB krivacsz to previous | to last
142 06-Jun-2025 05:34 8.752 kB krivacsz to previous | to last
141 06-Jun-2025 05:05 8.56 kB krivacsz to previous | to last
« This page (revision-146) was last changed on 06-Jun-2025 07:49 by krivacsz
G’day (anonymous guest)
CrushFTP11 | What's New

Referenced by
LeftMenu

JSPWiki