Bug 1229377
| Summary: | Evolution asks for password for GOA Calendar with OAuth2 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jiri Koten <jkoten> | ||||
| Component: | evolution-data-server | Assignee: | Milan Crha <mcrha> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 7.2 | CC: | jkoten, mcrha | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | evolution-data-server-3.12.11-23 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Cause: unneeded password prompt for CalDAV calendars configured in GOA using OAUth2 authentication
Consequence: sometimes was incorrectly detected that certain GOA configured calendar has OAuth2 authentication and it was asked for password, which shouldn't be done with OAuth2
Fix: correct the detection of OAuth2 authentication method being used
Result: password is not required, the connection to the server fails with an error instead
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-11-19 07:59:11 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Jiri Koten
2015-06-08 14:55:53 UTC
From the side investigation, the calendar itself (when it's working) has set: [Authentication] Host=apidata.googleusercontent.com Method=OAuth2 but the main .source of the GOA account has set: [Authentication] Host= Method=none Created attachment 1036447 [details] debug eds patch This should address the issue, it's a backported change currently living in the upstream sources. I made a scratch build with it. I'd like to ask you to install it [1] and run the evolution-calendar-factory from a terminal, to see whether the password prompt condition was hit (there is a g_message() call which prints a message on the console when the condition was satisfied). The command looks like: $ /usr/libexec/evolution-calendar-factory -w You can create also a script instead of the binary to have the output logged also when the service is started by the D-Bus itself, which can be done in a similar was as in bug #1171770 comment #21, skipping step a) and doing the same only without valgrind and with 'calendar' instead of 'addressbook' in the steps. [1] https://brewweb.devel.redhat.com/taskinfo?taskID=9322982 I got only once in a week the password prompt for the google account, but I haven't seen the message in the logs. Also this time I didn't have to restart the backend, the calendar continues to work normally after I dismissed the prompt. The log contains only following warnings: (evolution-calendar-factory.orig:5474): e-cal-backend-caldav-WARNING **: Server did not response with 207, but with code 6 (SSL handshake failed) CalDAV - failed to retrieve bunch of items 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-2015-2226.html |