Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have installed pGina on windows XP machine. I logged in as LDAP user and then changed the password. But next time when I login, I used the new password, but it doesn't work. I can still authenticate using old password.
But in linux machine, If I change password, it accepts the changes immediately and accepts new password.
So, here I doubt on onething. The pGina doesn't sync to LDAP server each time. That is why, even I have changed the LDAP password of an user, it still logs in using old password.
I woudl suggest running wireshark on the server side (or capture with tcpdump and then export the capture to wireshark somewhere else) and look at the ldap interactions when you change the password, see if there acutally is any, and if so, what the operations performed actually are. It doesn't make sense that there should be a cache within pGina, it's meant to be a pure client.
Yes. I found it to be a pure client issue. The pGina software which is installed in the windows XP machine doesn't even connect to LDAP server when the LDAP username is already present in the machine. Actually, when a LDAP user logs in for first time, it first checks the local account. If the username is not found, then it contacts the LDAP server. So, once it authenticates LDAP user, it creates an account in the local machine. So when the same user logs in next time, it doesn't contact the LDAP server, but it checks the local authentication and authenticates. So, if the LDAP user password is changed in the LDAP server , it doesn't make sense. We are still able to login to the client using old password. I believe this is a bug in pGina and it should be addressed as it is a serious matter.
Did any one encounter this issue? Or any one using this software for authenticating LDAP users on windows machine?
I would like to know other methods of LDAP client authentication in Windows.
Looking over the pGina docs, i'm not sure it's so much a bug, but a glaringly stupid feature. The docs are amazingly thin on the ground for such a potentially useful tool.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.