Hey Chandan, I tried your guide and am still getting the same issues with the CA not being trusted. How do I make the certificate trusted to the client? Also, my main goal is to be able to create a new user on LDAP on the server side (with POSIX attributes) and then when I try to log in for the first time on the client machine, it should find the information in the LDAP server and let me login as a newly created user. Have you tried doing this before? When I did a id <ldap-userid" on the client side, it was returning values for me for EXISTING user accounts on the client side, but nothing on users I didn't have already created on the client side. How do I get this to work? I have been banging my head on this for way too long! Thanks, Rohit From: Chandan Kumar <chandank.kumar@xxxxxxxxx> Reply-To: "General discussion list for the 389 Directory server project." <389-users@xxxxxxxxxxxxxxxxxxxxxxx> Date: Thursday, December 13, 2012 1:57 PM To: "General discussion list for the 389 Directory server project." <389-users@xxxxxxxxxxxxxxxxxxxxxxx> Subject: Re: How to set up 389 client Unknown CA means the certificate that you have copied to client machine is not trusted. Please make sure there are no typos in the sssd.conf file for the certificate directory path or at the ldap.conf path. Also if you want to check whether you ldap auth is working, just do "id <ldap-userid>" it should show the information. If it does not then please check your nssswitch.conf and sssd parameters. In my case, the ldapsearch was throwing error with certificates, however, sssd user authentication was working perfect. On Thursday, December 13, 2012, Chaudhari, Rohit K. wrote:
-- -- |
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
