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 183.3 kB 3 13-May-2025 03:01 krivacsz
png
 »credential_config_gdrive.png 172.3 kB 1 15-May-2025 05:00 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-137) was last changed on 04-Jun-2025 01:28 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 1 added one line
\\
At line 2 changed one line
__Google Mail__ through __SMTP__/__IMAP__ requires __OAuth 2.0__ ([OAuth Wikipedia Link|https://en.wikipedia.org/wiki/OAuth]) for authentication. (More information : [Google IMAP-SMTP Link|https://developers.google.com/gmail/imap/imap-smtp]).\\
__Google Mail__ through __SMTP__/__IMAP__ requires __OAuth 2.0__ ([OAuth Wikipedia Link|https://en.wikipedia.org/wiki/OAuth]) for authentication. This is part of Google’s effort to enhance security by deprecating less secure app access (basic authentication using just a username and password). OAuth 2.0 offers a more secure, token-based system that supports modern features like multi-factor authentication, granular permission scopes, and token expiration for better protection against credential theft. For technical implementation details, see Google’s documentation here : [Google IMAP-SMTP Link|https://developers.google.com/gmail/imap/imap-smtp].\\
At line 4 changed 2 lines
__!!! Proxy Configuration:__ If your server accesses the internet through a proxy, make sure to whitelist the following domains for Google Mail Authentication:\\
• oauth2.googleapis.com\\
__⚠️ Proxy Configuration:__ If your server accesses the internet through a proxy, make sure to whitelist the following domains for Google Mail Authentication: __oauth2.googleapis.com__\\
At line 8 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]\\
__⚠️ Note:__ Ensure sure the __GMAIL API__ is enabled at __Enabled APIs & services__. [Google API Library Link|https://console.cloud.google.com/apis/library]\\
At line 18 changed one line
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. 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__.\\
At line 23 changed 4 lines
}}}\\
or
{{{
or
At line 28 removed one line
At line 27 added one line
\\
At line 36 added 3 lines
__⚠️ Note:__ You can configure the __OAuth consent screen__ by clicking the link above the __Authorized JavaScript origins__ section:\\
"The domains you enter in the fields below will be automatically added to your __OAuth consent screen__ as __authorized domains__."\\
Click the link to open the __OAuth consent screen__ settings, complete the configuration, and authorize your __CrushFTP domain.__\\
At line 55 changed one line
[attachments|oauth_form.png]\\
[SMTP Google Mail Integration/oauth_form.png]\\
At line 76 added 2 lines
[SMTP Google Mail Integration/pop_imap_task.png]\\
\\
At line 80 changed 3 lines
If the __Host__ contains __gmail.com, the corresponding __Get Refresh Token__ button will appear.\\
Configure the __App registration__. See at [Microsoft Mail via OAuth 2.0|https://www.crushftp.com/crush11wiki/Wiki.jsp?page=SMTP%20Microsoft%20Graph%20XOAUTH%202%20Integration#section-SMTP+Microsoft+Graph+XOAUTH+2+Integration-1.MicrosoftMailViaOAuth2.0]\\
__!!! Note__: To obtain the Refresh Token, the CrushFTP WebInterface’s host and port must match the Redirect URL specified in the Azure App Registration. In our example, it was: http://localhost:9090 or https://your.crushftp.domain.com/\\
If the __Host__ contains __gmail.com__, the corresponding __Get Refresh Token__ button will appear.\\
Configure the __1. Google Mail OAuth 2.0__ [Link|https://www.crushftp.com/crush11wiki/Wiki.jsp?page=SMTP%20Google%20Mail%20Integration#section-SMTP+Google+Mail+Integration-1.GoogleMailOAuth2.0]\\
At line 84 changed one line
Click on __Get Refresh Token__ button. Enter the __Client ID__ (See at App Registration -> Overview -> Application (client) ID), __Client Secret__ (See at App Registration -> Manage -> Certificates & secrets) make sure to copy the __value__ field, not the ID, and __Tenant ID__ (See at App Registration -> Overview -> Directory (tenant) ID). Proceed with the authentication and authorization process.
__⚠️ 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/\\
At line 86 changed 2 lines
__!!! Note__: Be sure to sign in with the __Microsoft Account__ that has the __necessary permissions__, as configured in the Azure App Registration mentioned above.\\
Since the email address is required after obtaining the refresh token, the Mail Username field must be adjusted.\\
Enter the __Client ID__ , __Client Secret__. Proceed with the authentication and authorization process. __!!! 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__.\\
\\
[SMTP Google Mail Integration/oauth_form.png]\\
\\
If the domain is unverified, a warning message may appear. Click __Advanced__ and choose to proceed:\\
\\
[SMTP Google Mail Integration/not_verified_domain.png]\\
\\
Click on the __Allow__ button:\\
\\
[SMTP Google Mail Integration/allow_form.png]\\
\\
__⚠️ Note:__ Since the email address is required after obtaining the refresh token, the Mail Username field must be adjusted.\\
At line 94 changed one line
[attachments|pop_imap_task.png]\\
For more information, see the general POP/IMAP Task description: [POP/IMAP Task – CrushFTP Documentation Link| https://www.crushftp.com/crush11wiki/Wiki.jsp?page=CrushTask#section-CrushTask-POP3IMAP]\\
At line 96 removed 2 lines
More info: [Link| https://www.crushftp.com/crush11wiki/Wiki.jsp?page=CrushTask#section-CrushTask-POP3IMAP]\\
\\
Version Date Modified Size Author Changes ... Change note
137 04-Jun-2025 01:28 8.493 kB krivacsz to previous
136 04-Jun-2025 01:19 8.407 kB krivacsz to previous | to last
135 04-Jun-2025 01:19 8.412 kB krivacsz to previous | to last
134 04-Jun-2025 01:18 8.407 kB krivacsz to previous | to last
133 04-Jun-2025 01:15 8.406 kB krivacsz to previous | to last
132 04-Jun-2025 01:15 8.575 kB krivacsz to previous | to last
131 04-Jun-2025 01:14 8.477 kB krivacsz to previous | to last
130 02-Jun-2025 02:20 8.481 kB krivacsz to previous | to last
129 02-Jun-2025 02:16 8.192 kB krivacsz to previous | to last
128 02-Jun-2025 02:11 8.191 kB krivacsz to previous | to last
127 02-Jun-2025 02:10 8.179 kB krivacsz to previous | to last
126 02-Jun-2025 02:09 8.084 kB krivacsz to previous | to last
125 02-Jun-2025 02:08 7.976 kB krivacsz to previous | to last
124 01-Jun-2025 11:28 7.929 kB krivacsz to previous | to last
123 01-Jun-2025 11:27 7.922 kB krivacsz to previous | to last
122 01-Jun-2025 11:24 7.914 kB krivacsz to previous | to last
121 01-Jun-2025 11:22 7.911 kB krivacsz to previous | to last
« This page (revision-137) was last changed on 04-Jun-2025 01:28 by krivacsz
G’day (anonymous guest)
CrushFTP11 | What's New

Referenced by
LeftMenu

JSPWiki