[kaddressbook] [Bug 315048] New: LDAP Search w/GSSAPI yields 'Unknown API Error'

[Paul Sobey]

https://bugs.kde.org/show_bug.cgi?id=315048

            Bug ID: 315048
           Summary: LDAP Search w/GSSAPI yields 'Unknown API Error'
    Classification: Unclassified
           Product: kaddressbook
           Version: 4.10
          Platform: Gentoo Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: ldap search
          Assignee: kdepim-bugs at kde.org
          Reporter: buddha at the-annexe.net
                CC: tokoe at kde.org

Using kaddressbook, I have defined an ldap search against our internal MS
Active Directory (Win 2008) service, with GSSAPI bindings. I am trying to
achieve email address lookups for internal employee addresses.

Running on a gentoo platform with ldap/kerberos/sasl use flags. Kerberos
credentials on the box are valid and other kerberised services (e.g. nfs/krb5)
work fine.

At some point in the recent past (4.8 series I think), this worked, so I think
I'm seeing a regression. Hasn't worked through 4.9/4.10.

Reproducible: Always

Steps to Reproduce:
1. Install kdebase-meta and kdepim-meta on gentoo with ldap/sasl/kerberos/mysql
use flags
2. Define ldap service using the kontact/configure kaddressbook/LDAP Server
Settings interface
3. Leave user/bind dn/password blank. Fill in realm, host, leave 'security'
blank, and 'authentication' sasl/gssapi
4. Send mail in kmail, 'select recipients', 'search directory service', enter
search term, press search
Actual Results:  
Error dialogue with the text 'Unknown API error' and an ldap URL ending in
'mech=GSSAPI,x-sasl', no search results.

Expected Results:  
List of matching AD names and email addresses, autocompletion to work on the
kmail address entry dialogue.

As stated above, this worked well in 4.8, although auto-completion is somewhat
related to existing akonadi/nepomuk completion bugs (see KDE Bug #259949).

I may be dreaming, but I think the mechanism for configuring ldap address books
has changed recently. I used to have to define an ldap address source using the
Akonadi Configuration dialogue. Now I no longer have the option to do this, and
using the kaddressbook interface seems to be the only way. I'm not sure if
these UI changes are related and some piece of configuration isn't being
properly filled in, or there is another problem.

As an additional note, I get the same result when targetting a kerberised
openldap service at home, so this is not MS AD specific.

For what it's worth, versions of relevant components installed are:

app-crypt/mit-krb5: 1.9.4-r1
net-nds/openldap: 2.4.30
dev-libs/cyrus-sasl: 2.1.25-r3
kde-base/kdepimlibs: 4.10.0-r1

I filed this here rather than in gentoo's bug tracker as it feels like a
KDE-wide problem, but I can take it to the gentoo tracker if more appropriate.

-- 
You are receiving this mail because:
You are the assignee for the bug.