lists.arthurdejong.org
RSS feed

No output from getent netgroup

[Date Prev][Date Next] [Thread Prev][Thread Next]

No output from getent netgroup



Hi,

i replaced libnss-ldap and libpam-ldap with libnss-ldapd and libpam-ldapd in Ubuntu 22.04.

Looking up users and groups is no problem, but I get no output with netgroups. This works fine with the older ldap modules, but not with nslcd. Example:

# getent.ldap netgroup meitnerc
#


This is the debug output from nslcd:

nslcd: [b141f2] DEBUG: connection fromĀ  pid=4262 uid=0 gid=0
nslcd: [b141f2] <netgroup="meitnerc"> DEBUG: myldap_search(base="ou=Netgroup,dc=student,dc=lth,dc=se", filter="(&(objectClass=nisNetgroup)(cn=meitnerc))") nslcd: [b141f2] <netgroup="meitnerc"> DEBUG: ldap_result(): cn=meitnerc,ou=Netgroup,dc=student,dc=lth,dc=se nslcd: [b141f2] <netgroup="meitnerc"> DEBUG: ldap_result(): end of results (1 total)

If I use the same searchbase and filter with ldapsearch it looks fine:

# ldapsearch -x -b ou=Netgroup,dc=student,dc=lth,dc=se -H ldap://ldap.ddg.lth.se "(&(objectClass=nisNetgroup)(cn=meitnerc))"
# extended LDIF
#
# LDAPv3
# base <ou=Netgroup,dc=student,dc=lth,dc=se> with scope subtree
# filter: (&(objectClass=nisNetgroup)(cn=meitnerc))
# requesting: ALL
#

# meitnerc, Netgroup, student.lth.se
dn: cn=meitnerc,ou=Netgroup,dc=student,dc=lth,dc=se
objectClass: top
objectClass: nisNetgroup
cn:: bWVpdG5lcmMgICAg
nisNetgroupTriple: (meitner-1.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-2.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-3.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-4.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-5.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-6.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-7.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-8.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-9.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-10.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-11.fys.lth.lu.se,,)
nisNetgroupTriple: (meitner-12.fys.lth.lu.se,,)

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1

Any clue to what the problem is? Could it have something to do with our openldap returning cn base64 encoded?

/Per