Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1326634 - GOA configured Google calendar not using OAuth2
GOA configured Google calendar not using OAuth2
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution-data-server (Show other bugs)
7.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Milan Crha
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-13 05:14 EDT by Vladimir Benes
Modified: 2016-11-03 20:25 EDT (History)
2 users (show)

See Also:
Fixed In Version: evolution-data-server-3.12.11-30.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-03 20:25:46 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2206 normal SHIPPED_LIVE evolution-data-server bug fix update 2016-11-03 09:23:16 EDT

  None (edit)
Description Vladimir Benes 2016-04-13 05:14:42 EDT
Description of problem:
there is an issue of connection to google calendar via GOA. It says that it doesn't have password from time to time. Should be related to:
https://bugzilla.gnome.org/show_bug.cgi?id=728496

Version-Release number of selected component (if applicable):
evolution-data-server-3.12.11-28.el7.x86_64

How reproducible:
sometimes
Comment 1 Milan Crha 2016-04-13 10:04:25 EDT
I fixed this for evolution-data-server-3.12.11-30.el7 with a similar change as this one upstream [1].

[1] https://git.gnome.org/browse/evolution-data-server/commit/?id=4b14c7e
Comment 5 errata-xmlrpc 2016-11-03 20:25:46 EDT
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

Note You need to log in before you can comment on or make changes to this bug.