Per Qvindesland wrote: > Hi > > Thanks so much for responding to my post. > > I managed to find out this but from what I don't get is why after having > installed and configured clients to authenticate towards the server > correctly they still don't do it, I have looked for any log files that could > give me some clue of what I have done rong but no luck the error log in the > admin interface says nothing that is of use, I have also read the manual > from one side to the other but I can not find anything that tells me what > steps that I have been forgetting. > > Is there any error logs that it generats that it generates that can give me > some more clues? > I'm not sure where pam and nss log - possibly /var/log/secure You can see what searches are being performed against the directory server by looking at /var/log/dirsrv/slapd-yourinstance/access > Regards > Per Qvindesland > > > On 1/28/09 4:37 PM, "Rich Megginson" <rmeggins at redhat.com> wrote: > > >> Per Qvindesland wrote: >> >>> Hi List >>> >>> After having installed Directory Server with no problems and created a test >>> user account I then go ahead to configure a client to test the >>> authentication to my new directory server, sadly after a reboot I can't >>> login with my new user account that I created, I have spent a few days >>> reading up about what the problem may be but until now I have had very >>> little joy. >>> >>> If I try ldapsearch -v then I get error message: >>> SASL/EXTERNAL authentication started >>> Ldap_sasl_interactive_bind_s:unknown authentication method (-6) >>> additional info: SASL(-4): no mechanism available: >>> >>> >> This is because the openldap ldapsearch client attempts SASL >> authentication by default. You have to specify -x to make it use simple >> (username/password or anonymous) authentication. >> >>> If i use ldapsearch -x then I get the output of a ldif file with all groups, >>> users and domains available so there is apparently nothing rong with the >>> communication, I truly belive that this is a security problem that sits >>> somewhere but I have no idea. >>> >>> >> I don't think this is a security problem. >> >>> Could anyone give me some pointers to how I could fix this problem? >>> >>> Regards >>> Per Qvindesland >>> >>> >>> -- >>> Fedora-directory-users mailing list >>> Fedora-directory-users at redhat.com >>> https://www.redhat.com/mailman/listinfo/fedora-directory-users >>> >>> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-users >> > > > -- > Fedora-directory-users mailing list > Fedora-directory-users at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3258 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.fedoraproject.org/pipermail/389-users/attachments/20090129/609d1a7d/attachment.bin
