** Changed in: libnss-ldap (Ubuntu)
Status: New = Triaged
** Changed in: libnss-ldap (Ubuntu)
Importance: Undecided = Low
--
LDAP and AD connection problem with hardy
https://bugs.launchpad.net/bugs/227229
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: libnss-ldap (Ubuntu)
Status: New = Triaged
** Changed in: libnss-ldap (Ubuntu)
Importance: Undecided = Low
--
LDAP and AD connection problem with hardy
https://bugs.launchpad.net/bugs/227229
You received this bug notification because you are a member of Ubuntu
Bugs,
Indeed, while writing the post, I didn't realize that these are
different packages.
libnss-ldap - NSS module for using LDAP as a naming service
libnss-ldapd - NSS module for using LDAP as a naming service
They look very similar, and probably I mixed up the two packages while
installing ldap
Indeed, while writing the post, I didn't realize that these are
different packages.
libnss-ldap - NSS module for using LDAP as a naming service
libnss-ldapd - NSS module for using LDAP as a naming service
They look very similar, and probably I mixed up the two packages while
installing ldap
Intrepid has a different nss-ldap configuration than hardy.
There is a deamon nslcd in the package libnss-ldapd, which has its own
config file /etc/nss-ldapd.conf with a different syntax (not compatible
to Hardy's /etc/ldap.conf).
I use the following filter statement for the groups. I am not an
slithy, kunzol above is wrong: nss-ldapd is indeed available in 8.04,
but it is not default and does not supersede libnss-ldap. It is a
completely different package than libnss-ldap (although it fill the same
use-case). I understand this bug concern libnss-ldap, not libnss-
ldap*d*.
--
LDAP
Oh, I didn't realize he was talking about a different package.
--
LDAP and AD connection problem with hardy
https://bugs.launchpad.net/bugs/227229
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in ubuntu.
--
Intrepid has a different nss-ldap configuration than hardy.
There is a deamon nslcd in the package libnss-ldapd, which has its own
config file /etc/nss-ldapd.conf with a different syntax (not compatible
to Hardy's /etc/ldap.conf).
I use the following filter statement for the groups. I am not an
Hmm, I don't have that daemon running or installed (no startup script in
/etc/init.d and no /etc/nss-ldap.conf).
[EMAIL PROTECTED]:~$ apt-cache policy libnss-ldap
libnss-ldap:
Installed: 260-1ubuntu2
Candidate: 260-1ubuntu2
Version table:
*** 260-1ubuntu2 0
500
slithy, kunzol above is wrong: nss-ldapd is indeed available in 8.04,
but it is not default and does not supersede libnss-ldap. It is a
completely different package than libnss-ldap (although it fill the same
use-case). I understand this bug concern libnss-ldap, not libnss-
ldap*d*.
--
LDAP
Oh, I didn't realize he was talking about a different package.
--
LDAP and AD connection problem with hardy
https://bugs.launchpad.net/bugs/227229
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have encountered this bug as well.
First I ran into this bug on Hardy, which I built libnss-ldap from
source to solve it. Now I'm facing the same problem on Intrepid, so it
seems like something is up.
Looking at kunzol's fix, I am mapping the msSFU30GidNumber to gid as
well and making a
I have encountered this bug as well.
First I ran into this bug on Hardy, which I built libnss-ldap from
source to solve it. Now I'm facing the same problem on Intrepid, so it
seems like something is up.
Looking at kunzol's fix, I am mapping the msSFU30GidNumber to gid as
well and making a
Great, it woks!
But I did it in a different way.
I have the SFU installed on my AD and this includes the attribute
msSFU30GidNumber, which I use for the UNIX GID. Now I set up a
nss_base_group which filters out all groups without this attribute.
nss_base_group
I confirm this one.
The problem is that even thought there is this line in the ldap.conf
nss_map_objectclass posixGroup group
It will still recognise the AD groups which are not POSIX one's. This will lead
it to error with the GID's.
I made my work-around with
nss_base_group
I confirm this one.
The problem is that even thought there is this line in the ldap.conf
nss_map_objectclass posixGroup group
It will still recognise the AD groups which are not POSIX one's. This will lead
it to error with the GID's.
I made my work-around with
nss_base_group
I had similar problems which seemed to be caused by 1 of the groups in AD not
having a GID assigned.
Try assigning a GID to every group the user is a member of, don't forget nested
groups.
--
LDAP and AD connection problem with hardy
https://bugs.launchpad.net/bugs/227229
You received this bug
17 matches
Mail list logo
