Red Hat Bugzilla – Bug 169768
Evolution authentication failure for password containing a +
Last modified: 2007-11-30 17:11:14 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; (R1 1.5); .NET CLR 1.1.4322)
Description of problem:
When trying to setup my exchange account in evolution (as you do the first type you run it) I cannot authenticate against the server.
I can connect to the server using the same password using MS Outlook, OWA, Evolution 1.4 (RHEL3).
After some investigation it seems that if my password contains an + symbol then evolution (account wizard) will fail to authenticate me. If not, all works ok.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install FC4
2. Set your exchange password to have a + in it
3. Start Evolution
4. Go through the add account wizard, select MS Exchange as your server
5. Click Authenticate.
Actual Results: Authentication failure
Expected Results: Authentication accepted
Thanks for this bug report.
To isolate the problem further, it will be useful to know what kind of
authentication is being tried. What are the settings in use in Evolution 1.4 ?
Do you know if the server is using Forms Based Authentication?
The server is using Forms Based Authentication.
I should have also mentioned that Evolution 2.0 (RHEL4) also authenticates ok.
The settings for evolution 1.4 and 2.0...
Exchange Server: exchangeserver.domainname
Windows Username: username
Never Use SSL connection
Secure Password for authentication
Mailbox name: username
OWA path: /exchange
Public folder server: exchangeserver.domainname
The settings for evolution 2.2...
Is this problem still present in Fedora Core 6 or later?
The distribution against which this bug was reported is no longer supported,
could you please reproduce this with the updated version of the currently
supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue
turns out to still be reproducible, please let us know in this bug report. If
after a month's time we have not heard back from you, we will have to close this
bug as INSUFFICIENT_DATA.
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
Closing as INSUFFICIENT_DATA.