After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 708730 - CalDAV: Improve handling of invalid access tokens
CalDAV: Improve handling of invalid access tokens
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Calendar
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[goa] evolution[google] 3.10.1
Depends on:
Blocks:
 
 
Reported: 2013-09-25 10:31 UTC by Debarshi Ray
Modified: 2013-11-04 12:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
CalDAV patch (4.23 KB, patch)
2013-09-25 17:31 UTC, Matthew Barnes
committed Details | Review

Description Debarshi Ray 2013-09-25 10:31:39 UTC
When I am using a GOA account that offers a GoaCalendar interface, I am sometimes greeted by a gnome-shell modal dialog that asks me for my password. This should not happen because my credentials are already present in GOA.

I don't know how to reliably reproduce this, but it has happened to me under the following situations:
 - Just after adding the account
 - Just after deleting the account
 - Using the gnome-shell overview to search

I suspect this is EDS' calendar-factory because if I turn off calendars for the account, it doesn't happen anymore. But since I can't reliably reproduce it, I haven't been able to dig deeper.
Comment 1 Matthew Barnes 2013-09-25 12:14:17 UTC
Need to see a HTTP log for the calendar showing at least the auth headers.

https://wiki.gnome.org/Apps/Evolution/Debugging#CalDAV
Comment 2 Matthew Barnes 2013-09-25 17:31:56 UTC
Created attachment 255711 [details] [review]
CalDAV patch

I think this should avoid the password prompt on Bearer authentication failures.  I don't have easy access to GOA so I could use a volunteer to help verify this.
Comment 3 Milan Crha 2013-09-26 10:17:14 UTC
What about soup_message_set_status_full? It does propagate error messages through status pretty easily.
Comment 5 Debarshi Ray 2013-11-04 12:28:37 UTC
*** Bug 709430 has been marked as a duplicate of this bug. ***