Bug 160023 - GAL access fails authentication
GAL access fails authentication
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: evolution-connector (Show other bugs)
3
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Malcolm
http://bugzilla.gnome.org/show_bug.cg...
:
Depends On:
Blocks: FC4Update 160024
  Show dependency treegraph
 
Reported: 2005-06-09 23:09 EDT by Frank Pineau
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-05 09:28:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Desktop 269611 None None None Never

  None (edit)
Description Frank Pineau 2005-06-09 23:09:58 EDT
Description of problem:
Appears to be the same problem shown here
http://bugzilla.gnome.org/show_bug.cgi?id=269611
If I use user@domain, GAL will not work, calendars do work.

If I switch to domain\user, neither the GAL nor the calendars work.

Everything else seems to work OK.

The patch for this was committed to the 2.0.3 branch, but appears not to have
made it to the Fedora tree.

Backend is Exchange 2003 on Windows 2003 server, GC on a Windows 2000 domain
controller.  OWA is using forms-based authentication with SSL.

Version-Release number of selected component (if applicable):
2.0.4-1, 2.0.4-2

How reproducible:
Always

Steps to Reproduce:
1. Authenticate using user@domain method
2. Attempt to perform GAL lookup (contact list, new message auto-complete, etc.)

  
Actual results:
Setting E2K_DEBUG=4 shows

GC: Connecting to ldap://<my GC server>:3268/   
** (evolution-exchange-storage:12585): WARNING **: LDAP authentication 
failed (0x31)   

Expected results:
Authentication should work with either user@domain or domain\user.

Additional info:
Comment 1 Dave Malcolm 2005-08-18 01:23:35 EDT
Thanks for this report.  Is this still broken with the latest FC3 packages?
Comment 2 John Thacker 2006-05-05 09:28:34 EDT
The upstream bug report says it was fixed upstream.  Closing.
Should be in FC4 and FC5; FC3 is Fedora Legacy now.

Note You need to log in before you can comment on or make changes to this bug.