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 735197 - Evolution EWS periodically loses its authentication and repeatedly prompts for password, cannot reauth until a client restart
Evolution EWS periodically loses its authentication and repeatedly prompts fo...
Status: RESOLVED FIXED
Product: evolution-ews
Classification: Other
Component: Mail
3.12.x
Other Linux
: Normal major
: ---
Assigned To: Evolution EWS maintainer(s)
Evolution EWS maintainer(s)
: 738287 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-08-21 22:05 UTC by Jean-François Fortin Tam
Modified: 2015-09-03 16:45 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screenshot (77.98 KB, image/png)
2014-08-21 22:05 UTC, Jean-François Fortin Tam 		Details
EWS_DEBUG=2 (48.50 KB, text/x-log)
2014-08-21 22:07 UTC, Jean-François Fortin Tam 		Details

Description Jean-François Fortin Tam 2014-08-21 22:05:40 UTC 
Created attachment 284148 [details]
screenshot

It can happen just sitting around idle in the mail list, or when trying to send a mail I just composed: the EWS account eventually "disconnects" and refuses to let me check any messages or folders, prompts for the password, and then always consider the password as wrong until I restart Evolution.
Comment 1 Jean-François Fortin Tam 2014-08-21 22:07:40 UTC 
Created attachment 284149 [details]
EWS_DEBUG=2
Comment 2 Milan Crha 2015-03-04 18:44:34 UTC 
Thanks for a bug report. The attached log shows only successful responses (I do not count the first 404, because that's quite common).

Nonetheless, there is filled a similar downstream bug report [1] with an ongoing investigations, which seems to exhibit the same issue.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1196765
Comment 3 Milan Crha 2015-09-03 16:39:32 UTC 
According to the downstream bug report the issue had been fixed in libsoup, within Fedora with libsoup-2.48.1-2.fc21. I'm closing this as such.
Comment 4 Milan Crha 2015-09-03 16:45:40 UTC 
*** Bug 738287 has been marked as a duplicate of this bug. ***