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 270713 - Connector unusable because I can't change to plaintext auth
Connector unusable because I can't change to plaintext auth
Status: RESOLVED DUPLICATE of bug 270535
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.0.3
Other All
: Normal critical
: 2.0.4
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2004-12-21 06:40 UTC by Raul Acevedo
Modified: 2005-01-19 00:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Raul Acevedo 2004-12-21 06:40:13 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
My company's exchange server had to go down for maintenance, so I disabled
my exchange account in evolution.  This has resulted in four bugs in
evolution.  The last one is the most important.

bug#200001: it told me "This account will be disabled when you exit evolution."
 What???

I continued, and when the server came back, I restarted evolution,
re-enabled by exchange account, and then tried to create a new meeting request.

bug#200002: all attempts to schedule a meeting fail, because my entire schedule
--- and that for anyone else --- is grayed out.

bug#200003: I also noticed name completion in emails doesn't work for my
exchange account, even though contacts searches in the GAL work as before,
and even though everyone's schedule is grayed out in meeting requests, I
can click on "Contacts" and search for people to invite.

Anyway, here comes the real problem.  I figured I'd just delete my exchange
account and start over.

bug#200004: it doesn't work, because evolution insists, no matter how many
times I click on "plain text" authentication, to use Secure authentication.
 So whenever I type my password, it says "auth failed, try plain text",
which I select, but it doesn't work, because it always sets it right back
to secure auth.

Right now I can't use connector.  At all.  :(  Help!
Comment 1 Raul Acevedo 2004-12-21 19:48:14 UTC
As a different Unix user, I created a new Connector account and I get
the same problem as #4: it always says auth method of Secure Password,
no matter how many times I select plain text. 

Is there a quick and dirty fix for this, like setting the gconf key
for /apps/evolution/mail/accounts with XML that includes plain text in
the source or url tags?
Comment 2 Poornima 2004-12-22 12:31:15 UTC
Reg Bug:1: This message comes bcoz cleanup operation happens only when
you quit evolution. The error message needs to be fixed, the message
says your account will be removed even when user tries to 'disable'
the account.

Rest of the bugs i am not able to reproduce. More information would
help me to reproduce.
Comment 3 Gerardo Marin 2004-12-22 23:24:09 UTC
Raul: for future reference file a single report per bug, otherwise it
becomes hard to follow up every single solution.
Comment 4 Gerardo Marin 2004-12-28 18:47:00 UTC

*** This bug has been marked as a duplicate of 270535 ***
Comment 5 Raul Acevedo 2005-01-05 19:37:34 UTC
Sorry about filing it all in one bug report, I was just really
frustrated at having so many things go wrong at once over one simple
scenario.

In any case, turns out this is not a dupe of bug 270535.  I tried the
resolution for that, and it didn't work, I still get the same error
when I enter my password, even if I've manually updated the gconf key
to use plain text auth.  Here's the stdout of
evolution-exchange-storage... what's up with the
kerberos error???  I don't think keberos should be involved in any of
this.

# E2K_DEBUG=10
/home/garnome/2.8.1/libexec/evolution/2.0/evolution-exchange-storage
Evolution Exchange Storage up and running
E2K_DEBUG=10

(evolution-exchange-storage:6288): Gtk-WARNING **: Theme directory  of
theme Crystal-Raul has no size field

GET /exchange/racevedo/ HTTP/1.1
E2k-Debug: 0x8232780 @ 1104870401
Host: exchange.foo.com
Accept-Language: en-US, en
Authorization: NTLM
TlRMTVNTUAABAAAABoIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAwAAAA
User-Agent: Evolution/2.0.3

401 Access Denied
E2k-Debug: 0x8232780 @ 1104870401
Date: Tue, 04 Jan 2005 20:26:41 GMT
Server: Microsoft-IIS/5.0
Connection: close
Content-Length: 24
Content-Type: text/html


** (evolution-exchange-storage:6288): WARNING **: Unexpected kerberos
error -1765328230
Comment 6 Raul Acevedo 2005-01-06 23:02:44 UTC
Any progress, suggestions or workarounds for this?  I really, really
miss using Connector.  :(
Comment 7 Poornima 2005-01-07 07:47:19 UTC
bug 200004: where user is not able to change to 'Plain text' has to be
fixed. Even changes in %gconf.xml to 'Plain' doesnt change
authentication to 'Plain text', i will check if bug exists for this
else new bug will be raised to fix this issue
Comment 8 Raul Acevedo 2005-01-11 22:19:22 UTC
Someone suggested setting auth=Basic instead of auth=Plain in
~/.gconf/apps/evolution/mail/%gconf.xml.  That doesn't work for me
either; I get a dialog box saying "Could not connect to server
foo.exchange.com: Unknown error".  The stdout/stderr of
evolution-exchange-storage, started with E2K_DEBUG=10, shows:

GET /exchange/racevedo/ HTTP/1.1
E2k-Debug: 0x82367b8 @ 1105478114
Host: foo.exchange.com
Accept-Language: en-US, en
User-Agent: Evolution/2.0.3

403 Access Forbidden
E2k-Debug: 0x82367b8 @ 1105478114
Date: Tue, 11 Jan 2005 21:15:29 GMT
Server: Microsoft-IIS/5.0
Connection: close
Content-Length: 200
Content-Type: text/html

** (evolution-exchange-storage:27183): WARNING **: Unexpected kerberos
error -1765328230

This is different from what I posted above, in that it's no longer
trying to use NTLM... though I thought I needed NTLM auth to talk to
our exchange server, I remember that's why I originally had to find
the openldap RPM for connector.  Is NTLM different from plain text auth?

Anyway, the "kerberos error" is still showing up.  As I said
originally, we don't use kerberos (as far as I know), so I don't know
why that's showing up.

I don't know if SSL is configured on our exchange server.
Comment 9 Raul Acevedo 2005-01-19 00:01:04 UTC
Ok, turns out this really is a dupe of bug 270535.

I was screwing up the account information when creating the new
account.  I tried one more time to recreate my exchange account, but
this time used ximian-connector-setup, and when it asked me for the
OWA URL I realized this URL is different from the Exchange server URL.
 Apparently the OWA URL is the right one.  Ximian-connector-setup also
correctly uses auth=Basic.

*** This bug has been marked as a duplicate of 270535 ***