On 07/17/2012 11:13 AM, Arpit Tolani wrote:
Hello I don't think so. The original poster mentioned the Inactivate button. I assume this means using the Console feature to inactivate users. Users inactivated in this way should not just magically become re-activated. This is a problem. The problem with using plain ldapmodify is that it doesn't work with the mechanism used by the Console and the ns-inactivate.pl script, which use a Roles/CoS scheme to put inactive users into a specific Role and then use CoS to add nsAccountLock: TRUE to all members of that Role. The first step is to make sure that when you do a search of the supposedly inactive user's entry like this: ldapsearch -xLLL .... uid=inactiveuser \* nsAccountLock you see nsAccountLock: TRUE and then at some point in the future you see nsAccountLock: FALSE or just don't see it at all. When you say "log back in" - just after inactivating the user in the Console, did you verify that the user could not log in? And then did you at some point in the future see that the user could log in again? When you say "log back in" - do you mean the operating system login?
|
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users