Using access_provider = ldap causes failed loading of backend

[TerrySoucy]

Adding the following to sssd.conf results in the sssd backend failing to initialize...

access_provider = ldap
ldap_access_filter = memberOf=cn=engineering,cn=groups,cn=accounts,dc=internal,dc=blah,dc=com

Contents of logfile ...

[sssd[be[LDAP]]] [load_backend_module] (0): Unable to load init fn sssm_ldap_access_init from module ldap, error: /usr/lib/sssd/libsss_ldap.so: undefined symbol: sssm_ldap_access_init
[sssd[be[LDAP]]] [be_process_init] (0): Failed to setup ACCESS backend.
[sssd[be[LDAP]]] [main] (0): Could not initialize backend [80]

The message is a known issue with SSSD version < 1 and was apparently deemed to be a simple warning and was fixed, but I get no further in the startup, and sssd hangs at this point. Removal of the supported access provider option results in a working system.

Ubuntu Version --
Description: Ubuntu 10.04.4 LTS
Release: 10.04

Package Info --
sssd:
  Installed: 1.0.5-0ubuntu1
  Candidate: 1.0.5-0ubuntu1
  Version table:
 *** 1.0.5-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages
        100 /var/lib/dpkg/status

[Stephen Gallagher (stephen-gallagherhome)]

The LDAP access_provider option wasn't added in SSSD until 1.2.0.

The versions of SSSD still supported by upstream are:

1.5.x: Security fixes only, LTM
1.8.x: Fully supported, LTM
1.9.x Fully supported.

You're not going to see a major feature like this backported to 1.0.x ever.

[TerrySoucy (tsoucy)]

Crap. I though for sure that option was available in 1.0.5. Sorry for the false alarm.

[Timo Aaltonen (tjaalton)]

Terry: you might find 1.5.15 on this ppa useful:

https://launchpad.net/~sssd/+archive/updates