GNOME Bugzilla – Bug 327160
Exchange connector prompt for password twice during account setup
Last modified: 2012-02-02 14:38:17 UTC
Exchange connector once asks for password when user presses "Authenticate" button and once again at the end. The problem is key generated using the api camel_url_to_string (camel_url, CAMEL_URL_HIDE_PASSWORD | CAMEL_URL_HIDE_PARAMS); returns the key as https://user@host/ when invoked from plgin and https://user@host when invoked from mail-sessions's get_password() and so get_password in mail session again asks for the password. the key generated is not correct in mail-seesion as the URL it gets is not complete url.
Moving to mailer.
Can we always by default have the key stored as https://user@host always?
No, because, when you restart mailer will parse the URL and get the key as https://user@host/ and then exchange plugin will fail if it is hardcoded as https://user@host
Should investigate on why we need to have two different keys for the same account. What does the trailing-slash signify?
harmonizing target milestones, sorry for the noise. (2.6.x -> 2.6)
We don't need to have 2 different keys... Keys are formed from the URL in gconf and connector plugin and mailer forms it differently. Missing of trailing slash is the problem, keys are compared using string comapre api and they obviously do not match. Debugging little bit would help to understand it more.
Note that the package "evolution-exchange" is deprecated nowadays. Similar functionality is now provided by "evolution-mapi" and "evolution-ews" packages. This bug was reported against a version that is now not supported anymore. Could you please check if the problem that you reported here still happens with a recent version of Evolution (like 3.2 or 3.0) by reporting back and providing both your version and the package that you use? Thanks in advance!
Closing this bug report as no updated information has been provided. Please reopen this bug if the problem still occurs with a newer version of Evolution (currently this means: preferably version 3.2.x) and provide the information that was asked for in the previous comment. Again thank you for reporting this bug and we are sorry it could not be fixed for the version that you originally used when reporting this problem.