> On 24 Jan 2017, at 06:01, Darren Tucker <dtucker at zip.com.au> wrote: > > On Tue, Jan 24, 2017 at 4:54 PM, Vishwanath KC <vicchi.cit at gmail.com> wrote: > [...] >> Distributor ID: Debian >> Description: Debian GNU/Linux 8.2 (jessie) > > As you've seen, sshd requires that the system's getpwnam() function > knows the user, without which it does not know, for example, what > userid to run processes as should you manage to successfully > authenticate. > > You will need to either arrange for your system's NSS to know about > your users somehow or modify sshd.From memory, last time I got this working, we used NSS LDAP and PAM LDAP, and got public keys over LDAP too. It required some fiddling. -- Alex Bligh
> On 24 Jan 2017, at 06:53, Alex Bligh <alex at alex.org.uk> wrote: > > From memory, last time I got this working, we used NSS LDAP and > PAM LDAP, and got public keys over LDAP too. It required some > fiddling.With apologies for the quick followup, I think what we did was roughly this: https://shellpower.wordpress.com/2015/05/26/ssh-public-key-authentication-with-ldap-on-ubuntu/ -- Alex Bligh
Hi, Unfortunately we are not using NSS and LDAP. We are using only Tacacs server. The authentication needs to be done only via password. So please let me know how i can proceed on this. Regards, Vishwanath KC +918892599848. On Tue, Jan 24, 2017 at 12:26 PM, Alex Bligh <alex at alex.org.uk> wrote:> > > On 24 Jan 2017, at 06:53, Alex Bligh <alex at alex.org.uk> wrote: > > > > From memory, last time I got this working, we used NSS LDAP and > > PAM LDAP, and got public keys over LDAP too. It required some > > fiddling. > > With apologies for the quick followup, I think what we did was > roughly this: > > https://shellpower.wordpress.com/2015/05/26/ssh-public-key- > authentication-with-ldap-on-ubuntu/ > > -- > Alex Bligh > > > > >