I am stuck in the 389 DS implementation, hope someone could help me out.
My situation is that I am trying to establish a cute enterprise
environment with VMWorkstation and CentOS. All guest OSs are CentOS6.3
based. So far I have got DNS, DHCP, Gateway, File server worked
perfectly; However, the 389 LDAP server here, Hmm... I would say it is
partially working. And this is also where you come in.
What does it mean by 'partially working' exactly? Let me tell you.
What happened here is that I've installed and configured 389 DS without
SSL/TLS enable, migrated local users on my file server to the LDAP
already. Now, from my DHCP clients, also LDAP clients, I can retrieve
information within the LDAP server by running ldapsearch, I can even
change to regular users (i.e. user1/user2/.../user10 created on the file
server) with Autofs home directory mounted automatically. Somehow, I
cannot change password by running passwd command.
Here is what I got when changing.
[root@dhcpclient sssd]# /su - user1/
[user1@dhcpclient ~]$ /passwd/
Changing password for user user1.
passwd: Authentication token manipulation error
I am new to Linux, so have no idea about the reason behind that. Is it
a LDAP acl issue, or sssd configuration issue, or security pam issue, or
If you could help me out, that would be great. Please let me know if
you want any configuration files from me. I don't want to attach
everything here to scare you.
I am trying to get the passwordExpirationTime populated in a new 389ds instance. The users were imported from another instance of 389DS before I set the password policy. Is there an official way to fill in the passwordExpirationTime populated for all accounts on the server?
Senior Systems Administrator, Primatics Financial