Red Hat Bugzilla – Bug 1362674
CalDAV fails to recognize "Daily Limit Exceeded" error from Google/GOA
Last modified: 2016-11-03 20:25:57 EDT
Description of problem: Evolution-data-server periodically prompts for Google password via gnome-keyring-daemon. This represents a security concern, because the prompt requests secure credential information when such information is not expected to be required. Version-Release number of selected component (if applicable): evolution-data-server-3.12.11-24.el7.x86_64 How reproducible: Occurs periodically while logged in. Steps to Reproduce: 1. Add Google online account in Gnome 2. Use evolution, browse, do other stuffs, wait. Actual results: Occasionally prompt for Google password. Expected results: Should use saved credentials in gnome-keyring. Additional info: It appears this is caused by a change in the way Google performs authentication, and has been fixed in newer versions of evolution-data-server. evolution-data-server should be updated, or the following upstream patch backported to the version supplied in RHEL7: https://bugzilla.gnome.org/show_bug.cgi?id=735311#c3
See also this thread: https://ask.fedoraproject.org/en/question/51272/online-accounts-gmail-password-unexpectedly-fails/
Thanks for a bug report. The change you link to was released within the 3.12.6 version, thus it's already part of the current 3.12.11 version in the RHEL. That change is related to CalDAV only, thus for the Google calendars, it doesn't influence mail and other parts. Do you see the prompt for a Google calendar, or for other parts too. I'm unsure from your steps. If you see this on the mail account too, then I'd try to run evolution as: $ CAMEL_DEBUG=imapx:io evolution and then wait until you are prompted for the password for the Mail account. The last few lines should show what failed.
Odd. The symptoms I was seeing were identical to what was reported in those issues, so I assumed it had the same cause. I'll try to debug further and provide more information.
You might be facing [1], I'm pretty sure. I fixed this upstream and we can backport the change easily. It adds a new translatable string, but I do not consider it a problem. [1] https://bugzilla.gnome.org/show_bug.cgi?id=761450
(In reply to Milan Crha from comment #5) > You might be facing [1], I'm pretty sure. I fixed this upstream and we can > backport the change easily. It adds a new translatable string, but I do not > consider it a problem. > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=761450 It turned out that the change from this bug report was incomplete. I made more upstream fixes there, which I'll backport for the RHEL 7.3 after some testing.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2206.html