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 679303 - Doesn't detect when password has changed
Doesn't detect when password has changed
Status: RESOLVED FIXED
Product: evolution-ews
Classification: Other
Component: Miscellaneous / EWS Core
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Evolution EWS maintainer(s)
Evolution EWS maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-07-03 07:19 UTC by Milan Crha
Modified: 2012-07-03 17:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
ews patch (22.18 KB, patch)
2012-07-03 17:08 UTC, Milan Crha
committed Details | Review

Description Milan Crha 2012-07-03 07:19:39 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=836941

If the AD/Exchange password changes EWS doesn't detect that it's an auth issue.

First you get an HTTP error about connections exceeded then the following SSL error "Unable to retrieve message. No response: SSL handshake failed"

evolution-help-3.4.3-2.fc17.noarch
evolution-NetworkManager-3.4.3-2.fc17.x86_64
evolution-ews-3.4.3-1.fc17.x86_64
evolution-data-server-3.4.3-1.fc17.x86_64
evolution-mapi-3.4.3-5.fc17.x86_64
evolution-3.4.3-2.fc17.x86_64
Comment 1 Milan Crha 2012-07-03 17:08:49 UTC
Created attachment 217948 [details] [review]
ews patch

for evolution-ews (gnome-3-4 branch);

I cannot reproduce exactly this myself, but I can reproduce something close to it. My scenario is this:
a) successfully connected to ews server
b) meanwhile change password on the ews server
c) back in evolution try to do anything in the ews account
There was almost no recovery from this state, furthermore, even when I was reprompted for the password, then this was not used for following connection attempt, instead the old cached password on the EEwsConnection was used, thus no luck.

I think this (with the patch) works similar to IMAP. As soon as the server rejects, or just doesn't respond, the ews account disconnects and shows the error to the user (it shows "Authentication Failed" for me in c)). But, as soon as I try to repeat the action, or do any other, then the ews account reconnects to the server, and possibly asks for a new password.
Comment 2 Milan Crha 2012-07-03 17:10:51 UTC
Created commit e200e1a in ews master (3.5.4+)
Created commit 63846f8 in ews gnome-3-4 (3.4.4+)