Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0031937Openbravo ERPA. Platformpublic2016-01-19 09:542022-05-09 14:39
malsasua 
Triage Platform Base 
normalminoralways
scheduledopen 
20Community Appliance
 
 
Core
No
0031937: email configuration with gmail: it is necessary to enable the access without security in gmail configuration
in a client, when the email configuration is done with gmail account, the emails are not sent from OB. Email with the next error is returned:
Someone just tried to sign in to your Google Account test@gmail.com from an app that doesn't meet modern security standards.

You need to enable the access to gmail without security (see attachment)

Update: starting May 30, 2022, ​​Google will no longer support the use of third-party apps or devices which ask you to sign in to your Google Account using only your username and password, see https://support.google.com/accounts/answer/6010255?hl=en#:~:text=To%20help%20keep%20your%20account,or%20Google%20Cloud%20Identity%20customers. [^]
. go to client window -> tab:email configuration
 . configure it with a gmail account:
   smtp server: smtp.gmail.com
   smtp server account: your_account@gmail.com
   smtp server address: your_account@gmail.com
   smtp authentication: Y
   smtp connection security: SSL
   smtp port: 465

. enable one alert to send email and run alert process

error is returned:
 ERROR org.openbravo.erpCommon.utility.poc.EmailManager - javax.mail.AuthenticationFailedException: 534-5.7.14 <https://accounts.google.com/ContinueSignIn?sarp=1&scc=1&plt=AKgnsbthX [^]
 
 Please log in via your web browser and
534-5.7.14 then try again.
534-5.7.14 Learn more at
534 5.7.14 https://support.google.com/mail/answer/78754 [^] j3sm19403439wmj.19 - gsmtp

And email is sent to the account:
Sign-in attempt prevented:
Someone just tried to sign in to your Google Account miguel.alsasua@gmail.com from an app that doesn't meet modern security standards.
No tags attached.
related to design defect 0034991 acknowledged Triage Platform Base Mails are not sent when using gmail's SMTP configuration without letting insecure apps to access the account 
png gmailConf.png (191,249) 2016-01-19 09:56
https://issues.openbravo.com/file_download.php?file_id=8940&type=bug
png
Issue History
2016-01-19 09:54malsasuaNew Issue
2016-01-19 09:54malsasuaAssigned To => platform
2016-01-19 09:54malsasuaModules => Core
2016-01-19 09:54malsasuaTriggers an Emergency Pack => No
2016-01-19 09:56malsasuaFile Added: gmailConf.png
2022-02-01 08:09alostaleAssigned Toplatform => Triage Platform Base
2022-04-19 12:30PracticsIssue Monitored: Practics
2022-04-19 15:28AugustoMauchSeverityminor => critical
2022-04-19 15:28AugustoMauchTypefeature request => defect
2022-04-19 15:33AugustoMauchDescription Updatedbug_revision_view_page.php?rev_id=23926#r23926
2022-04-19 15:33AugustoMauchNote Added: 0136600
2022-04-20 10:24AugustoMauchNote Added: 0136620
2022-04-20 13:17AugustoMauchStatusnew => scheduled
2022-04-20 13:17AugustoMauchAssigned ToTriage Platform Base => ablasco
2022-04-25 15:41ivancaceresIssue Monitored: ivancaceres
2022-04-28 11:59shuehnerRelationship addedrelated to 0034991
2022-05-09 14:39AugustoMauchNote Added: 0137086
2022-05-09 14:39AugustoMauchAssigned Toablasco => Triage Platform Base
2022-05-09 14:39AugustoMauchSeveritycritical => minor

Notes
(0136600)
AugustoMauch   
2022-04-19 15:33   
Update to critical bug because of https://support.google.com/accounts/answer/6010255?hl=en#:~:text=To%20help%20keep%20your%20account,or%20Google%20Cloud%20Identity%20customers [^]
(0136620)
AugustoMauch   
2022-04-20 10:24   
See here how to use Oauth2 for server to server applications: https://developers.google.com/identity/protocols/oauth2/service-account?hl=en [^]
(0137086)
AugustoMauch   
2022-05-09 14:39   
Severity moved back to minor and SLA removed because we are going to follow a new approach that does not require modifications in our codebase.

Even though gmail will discontinue the use of username/passwords as authorization method for their smtp servers, the use of app passwords [1] will still be allowed.

[1] https://support.google.com/accounts/answer/185833?hl=en [^]