Timeline for Access denied for a particular user by PAM account configuration
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2021 at 10:44 | comment | added | okainov | @martin that's why I wrote that it's probably not a real solution. In the meantime in my case it was just my working PC, without any other "users", so I absolutely don't care whether I'll be able to prevent other users to login. | |
| Aug 21, 2021 at 9:01 | comment | added | Martin Kealey | "Workaround" is a kind word for this; I would be much less charitable. Disabling PAM means that if the user authenticates using an ssh key, you won't be able to prevent them from logging in by the "normal" method (disabling their account by marking it as "expired"). In most circumstances that would be a bad idea. As other answers have indicated, the problem is likely that the user who can't log in is probably disabled or missing in /etc/shadow. | |
| Oct 13, 2020 at 18:19 | comment | added | Thiago Conrado | funny enough, I have to servers that I just did install ubuntu 20 + ldap, one I did disable PAM and worked, in the other, it is working with it; the difference: one we have passwd shadows sync, in the other we do not... so seems that disabling PAM force it to use ldap login info... | |
| May 25, 2018 at 7:55 | history | answered | okainov | CC BY-SA 4.0 |