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 changed one line
!1.Google App Passwords\\
!1. Google App Passwords\\
At line 5 changed 3 lines
Google App Passwords are intended to provide limited access to less secure apps or legacy systems that cannot use OAuth 2.0 — primarily for Google services that use basic username/password authentication.
__⚠️ Note__:It requires 2 Factor to be enabled on the account.\\
Service can use App Passwords:\\
__⚠️ Constraints__: __It is only supported for accounts with 2-Step Verification enabled.__\\
At line 7 added 15 lines
Google App Passwords are intended to provide limited access to less secure apps or legacy systems that cannot use OAuth 2.0 — primarily for Google services that use basic username/password authentication.\\
__⚠️ 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.\\
\\
Service can use __App Passwords__:\\
__SMTP__: smtp.gmail.com\\
__IMAP__: imap.gmail.com\\
__POP3__: pop.gmail.com\\
\\
Create an app password: [Google App Password Link|https://myaccount.google.com/apppasswords]\\
\\
{{{
Username: your_email@gmail.com
Password: [your generated app password]
}}}
\\
At line 27 changed one line
The Redirect URL must end with __?command=register_google_mail_api__.\\
The __Redirect URL__ must end with __?command=register_google_mail_api__.\\
At line 59 changed 2 lines
__SMTP Server Username, Password__: If the SMTP server address ends with __gmail.com__, the corresponding __Get Refresh Token__ button will appear. Click that button to proceed.\\
__!!! 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/\\
__SMTP Server Username, Password__:\\
__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]\\
{{{
SMTP Server Username: your_email@gmail.com
SMTP Server Password: [your generated app password]
}}}\\
__b.)__ OAtuth 2.0: [2. Google Mail OAuth 2.0 Link|https://www.crushftp.com/crush11wiki/Wiki.jsp?page=SMTP%20Google%20Mail%20Integration#section-SMTP+Google+Mail+Integration-2.GoogleMailOAuth2.0] If the SMTP server address ends with __gmail.com__, the corresponding __Get Refresh Token__ button will appear. Click that button to proceed.\\
__⚠️ 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 62 changed one line
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 __SMTP Server Username__ and __SMTP Server Password__.\\
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 __SMTP Server Username__ and __SMTP Server Password__.\\
At line 74 changed one line
__From email address__: You must also specify the __From__ email address. __!!! Imnportant__ The __From__ address must exactly match __the signed-in Google user’s email address__ (i.e., the account used to obtain the refresh token). Otherwise, SMTP authentication will fail.\\
__From email address__: You must also specify the __From__ email address.\\
__⚠️ Imnportant__ The __From__ address must exactly match __the signed-in Google user’s email address__ (i.e., the account used to obtain the refresh token) or the account associated with the App Password. Otherwise, SMTP authentication will fail.\\
At line 92 removed one line
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 94 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/\\
__Mail Username, Password__:\\
__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]\\
{{{
Mail Username: your_email@gmail.com
Mail Password: [your generated app password]
}}}\\
__b.)__ OAtuth 2.0: Configure the [2. Google Mail OAuth 2.0 Link|https://www.crushftp.com/crush11wiki/Wiki.jsp?page=SMTP%20Google%20Mail%20Integration#section-SMTP+Google+Mail+Integration-2.GoogleMailOAuth2.0]\\
__⚠️ 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 96 changed one line
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__.\\
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__.\\
At line 144 added one line
----
At line 146 added one line
----
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