search for: samacccountnam

I have to assume much, I'll try. So... - No AD, that's some NT4 domain. - No Winbind because Winbind is using samacccountname as user login and not UID. - Issue happens on Linux or UNIX clients. The question is what tool (SSSD, pam_ldap / nss_ldap, nslcd...) are you using to retrieve information from LDAP to forge users on system side. Once you get an answer to this previous question check how to configure that tool t...

Sir, No AD, that's some NT4 domain. Yes, it has no AD - No Winbind because Winbind is using samacccountname as user login and not UID. --> Not configured > - Issue happens on Linux or UNIX clients. On both client I am using sssd and pam_ldap for user retrival and modified pam_login_attribute (pam_ldap.conf file) to username instead of uid (by default value) so I am very well able to authentic...

...> Verzonden: woensdag 12 oktober 2016 11:56 > Aan: mathias dufresne > CC: samba > Onderwerp: Re: [Samba] samba with customized ldap backend > > > Sir, > > > No AD, that's some NT4 domain. > Yes, it has no AD > > - No Winbind because Winbind is using samacccountname as user login and > not UID. > --> Not configured > > > - Issue happens on Linux or UNIX clients. > On both client > > > I am using sssd and pam_ldap for user retrival and modified > pam_login_attribute (pam_ldap.conf file) to username instead of uid (by > de...

...>> Aan: mathias dufresne >> CC: samba >> Onderwerp: Re: [Samba] samba with customized ldap backend >> >> >> Sir, >> >> >> No AD, that's some NT4 domain. >> Yes, it has no AD >> >> - No Winbind because Winbind is using samacccountname as user login and >> not UID. >> --> Not configured >> >>> - Issue happens on Linux or UNIX clients. >> On both client >> >> >> I am using sssd and pam_ldap for user retrival and modified >> pam_login_attribute (pam_ldap.conf file) to...

...CC: samba >>> Onderwerp: Re: [Samba] samba with customized ldap backend >>> >>> >>> Sir, >>> >>> >>> No AD, that's some NT4 domain. >>> Yes, it has no AD >>> >>> - No Winbind because Winbind is using samacccountname as user login and >>> not UID. >>> --> Not configured >>> >>>> - Issue happens on Linux or UNIX clients. >>> On both client >>> >>> >>> I am using sssd and pam_ldap for user retrival and modified >>> pam_logi...

...CC: samba >>> Onderwerp: Re: [Samba] samba with customized ldap backend >>> >>> >>> Sir, >>> >>> >>> No AD, that's some NT4 domain. >>> Yes, it has no AD >>> >>> - No Winbind because Winbind is using samacccountname as user login and >>> not UID. >>> --> Not configured >>> >>>> - Issue happens on Linux or UNIX clients. >>> On both client >>> >>> >>> I am using sssd and pam_ldap for user retrival and modified >>> pam_logi...

...; Aan: mathias dufresne > > CC: samba > > Onderwerp: Re: [Samba] samba with customized ldap backend > > > > > > Sir, > > > > > > No AD, that's some NT4 domain. > > Yes, it has no AD > > > > - No Winbind because Winbind is using samacccountname as user login and > > not UID. > > --> Not configured > > > > > - Issue happens on Linux or UNIX clients. > > On both client > > > > > > I am using sssd and pam_ldap for user retrival and modified > > pam_login_attribute (pam_ldap.conf fi...

...:56 >> Aan: mathias dufresne >> CC: samba >> Onderwerp: Re: [Samba] samba with customized ldap backend >> >> >> Sir, >> >> >> No AD, that's some NT4 domain. >> Yes, it has no AD >> >> - No Winbind because Winbind is using samacccountname as user login and >> not UID. >> --> Not configured >> >>> - Issue happens on Linux or UNIX clients. >> On both client >> >> >> I am using sssd and pam_ldap for user retrival and modified >> pam_login_attribute (pam_ldap.conf file) to use...

...: [Samba] samba with customized ldap backend >>>> >>>> >>>> Sir, >>>> >>>> >>>> No AD, that's some NT4 domain. >>>> Yes, it has no AD >>>> >>>> - No Winbind because Winbind is using samacccountname as user login and >>>> not UID. >>>> --> Not configured >>>> >>>>> - Issue happens on Linux or UNIX clients. >>>> On both client >>>> >>>> >>>> I am using sssd and pam_ldap for user retrival an...

Dear All, I have configured ldap with uid='some numeric' instead of uid=username like that; dn: uid=102220,ou=User,dc=example,dc=com uid: 102220 username: test1 cn: Test Account objectClass: inetOrgPerson objectClass: posixAccount objectClass: top objectClass: shadowAccount objectClass: sambaSamAccount mail: test1 at cdac.in shadowLastChange: 15587 loginShell: /bin/bash uidNumber: 5345