Bug 477808 - GSSAPI / Kerberos IMAP authentication broken in Evolution 2.24
Summary: GSSAPI / Kerberos IMAP authentication broken in Evolution 2.24
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 10
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-23 20:38 UTC by Dax Kelson
Modified: 2009-01-08 11:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-08 11:02:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 554182 0 None None None Never

Description Dax Kelson 2008-12-23 20:38:49 UTC
Description of problem:

It appears that Evolution 2.24.0 through at least evolution-2.24.2 fails to authenticate with GSSAPI / Kerberos with IMAP.

It does fetch an imap service ticket, but fails to use it.

This bug was reported in the GNOME bug tracker in Sept 2008 but no action has been taken there (yet).

Evolution 2.22 on Fedora 9 works perfectly fine with GSSAPI / Kerberos IMAP authentication.

Version-Release number of selected component (if applicable):
evolution-2.24.2-2.fc10.x86_64

How reproducible:
everytime

Steps to Reproduce:
1. Configure workstation in Kerberos REALM
2. Tell Evo 2.24 to use GSSAPI IMAP authentication

Comment 1 Matthew Booth 2008-12-29 00:16:25 UTC
Changing the priority from low to medium. This is a show-stopper for anybody hit by it (myself, for eg).

Comment 2 Milan Crha 2009-01-08 11:02:39 UTC
The upstream bug [1] contains a patch, which has been committed to the stable branch too, couple minutes ago. The fix will be available in the next release/update of evolution-data-server, version 2.24.3, which is planned around January 14th.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=554182


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