Let me close this thread by adding my solution. I feel rather foolish, but I failed to check the settings for my user in the LDAP server. They had been set months ago with a default loginShell of /bin/false.
So all the PAM configurations were correct which is why the logs indicated success. But when it tried to start a shell, /bin/false stopped everything and the session was closed. After changing to /bin/bash, my login succeeded. I have since found one website with an example that does add the session configuration mentioned below. But it works fine without it. I need to do further research to see what effect one has over the other. On Tue, 13 Apr 2004 09:52:25 -0700 Carlos Hanson <[EMAIL PROTECTED]> wrote: > None of the examples show that as a requirement. When I add that line, > I get the same results without a log showing a session opened and a > session closed. > > > On Tue, 13 Apr 2004 00:13:05 +0200 > Bob Schl�rmann <[EMAIL PROTECTED]> wrote: > > > > > Unless i miss something, why didn't you specify an ldap rule here too, > > like: > > > > session sufficient pam_ldap.so > > > -- Carlos Hanson Webmaster and Postmaster Tigard-Tualatin School District ph: 503.431.4053
