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 337498 - cannot authenticate to Global Catalog (GAL)
cannot authenticate to Global Catalog (GAL)
Status: RESOLVED DUPLICATE of bug 329371
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.6.0
Other All
: Normal normal
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2006-04-06 13:47 UTC by Bryan Cole
Modified: 2006-04-07 10:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Bryan Cole 2006-04-06 13:47:16 UTC
Please describe the problem:
When trying to access the GAL on an Exchange 2003 Server, Address book reports:
"Error loading addressbook.

We were unable to open this addressbook.  This either means you have entered an
incorrect URI, or the server is unreachable."

Using E2K_DEBUG=4 on the connector yields only:
"
GC: looking up info for bryan.cole@teraview.local

GC: Connecting to ldap://jupiter.teraview.local:3268/

** (evolution:26306): WARNING **: LDAP authentication failed (0x31)
"

Note, I can authenticate to this server using any other LDAP browser, using the
same bind DN and URL.

Steps to reproduce:
1. Setup an exchange account
2. try to access GAL
3. 


Actual results:


Expected results:


Does this happen every time?
yes

Other information:
Comment 1 Ryan Shea 2006-04-06 19:39:02 UTC
In Evolution 2.4 I would be prompted for my password to both mail and the calendar.  What seemed to happen was that if I selected "save my password", then when my password expired on the Exchange server, I would be prompted for my password again for mail, but not for the calendar.

This is related because at the same time this would happen I would no longer be able to perform lookups against the GAL.  I could not find a way to reset my password for the calendar (no idea why Evolution keeps them separately), so I had to remove and re-add the acccount to get it working again.
Comment 2 Bryan Cole 2006-04-06 20:02:49 UTC
I tried removing and re-creating the exchange account. Didn't make any difference. Still no joy.
Comment 3 Sushma Rai 2006-04-07 03:57:47 UTC
Bryan Cole, Can you try Evolution 2.6?

You can use File->Forget Passwords to forget all the 
remembered passwords, instead of re-creating the account.

Also, calendar is asking for password again, not because calendar
and mailer stores the passwords at different places, could be due to
some other bug.

You are able to access your calendars and Personal contacts?
Comment 4 Bryan Cole 2006-04-07 09:20:55 UTC
I am using 2.6.0 (in FC5).

I tried File->Forget Passwords, with no difference. Still can't authenticate to GAL.

I've done an ethereal capture on this: it seems Evo-connector is only passing my username 'bryan.cole' as the bind dn, instead of username@domain.

However, if I enter "username@domain" in the username field of the account configuration dialog, then connection to the email and calendar fails.

With just my username (no @domain) I'm able to access my calendars and personal contacts OK. However, I can't edit folder permissions or subscribe to other folders (I guess these operations require GAL lookups which explains these).

Comment 5 Bryan Cole 2006-04-07 09:43:06 UTC
OK. Problem solved!

I need to put my username in the account dialog in the form "domain\username". This is the 'old' (pre Exchange-2003) style; The best solution here is to make Connector handle 'username@domain' format properly. However, a workable interim measure would be to add some guidance in the account configuration dialog to make the format of the 'username' field explicit.

Now GAL lookups work and I can set permissions on my folders. Even subscriptions to other users folders seem to work (after restarting evo). Yeay.
Comment 6 Sushma Rai 2006-04-07 10:51:51 UTC
There is already a bug #329371. 

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