GNOME Bugzilla – Bug 677398
Can get stuck in e_book_backend_ews_authenticate_user()
Last modified: 2012-06-04 16:51:45 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=821228 EWS' address book can get stuck in authentication, possibly leading to a locked account on the server. The symptoms are that multiple threads in the factory process look like this:
+ Trace 230307
Thread 14 (Thread 0xadbf9b40 (LWP 30306))
Created attachment 215561 [details] [review] ews patch for evolution-ews; This is pretty interesting, as it happened between 3.4.1 and 3.4.2, and this was not caused directly by changes in ews. There was an issue with sender's photo being read from local only, and the option didn't influence behaviour in evolution. it was fixed in evo for 3.4.2. Once it is set to include also remote addressbooks, the the ews book is trying to authenticate. The problem is that when message is shown the contact's photo is looked up for, but this lookup doesn't authenticate books, thus the backends gets back ECredentials with no username nor password. This is used to indicate that password prompt failed, thus the backend can finish its opening phase, but EWS' backend didn't respond to it properly and rather tried to connect to he server again, with no username and password, thus it failed again. This way there was a very nice ping-pong on DBus, resulting in a repeated authentications against server from the addressbook factory each few seconds. I'm committing change to master too, but there only the piece of e-ews-connection.c, the rest is totally different now.
Created commit c28c9c1 in ews master (3.5.3+) Created commit 0cb2c55 in ews gnome-3-4 (3.4.3+)