> > The immediate reason for the failure should be found in the sshd logs in
> > /var. But the trick with LDAP for login authentication is this:

I'm probably making a mistake. I will try again from the beginning.
I'll pass the information.

Thanks.


On Tue, Oct 12, 2021 at 5:04 PM Henning Follmann
<hfollm...@itcfollmann.com> wrote:
>
> On Mon, Oct 11, 2021 at 06:04:08PM -0500, Nicholas Geovanis wrote:
> > On Mon, Oct 11, 2021, 7:31 AM Gokan Atmaca <linux.go...@gmail.com> wrote:
> >
> > > Hello
> > >
> > > I am using openldap. I configured a different server as ldap client.
> > > When I say "id user", the information comes. I have two organized
> > > units. "people" and "groups". my test environment.  But I can't login.
> > > What could be causing the problem?
> > >
> >
> > The immediate reason for the failure should be found in the sshd logs in
> > /var. But the trick with LDAP for login authentication is this:
>
> why should this be in the sshd logs?
>
> Is he/she even try to ssh into that machine and using openldap as a
> passwort store? Or a local login, httpd, email...
>
> He/she might even try to just login into ldap, from the post
> it is not clear what he/she is actually trying.
>
> >
> > (1) Make sure the services file is stepping thru the authentication
> > databases in the order you believe is correct.
> > (2) make sure name resolution is doing what you think it's doing.
> > (3) Make sure that clock time is synchronized across all servers involved
> > in that login and authentication.
> >
> >
> > Example:
> > > $ id gokhan (ldap_user)
> > > uid=10000(gokhan) gid=2000(ob) groups=2000(ob)
> > >
> > > Thanks.
> > >
> > >
> > > --
> > > ⢀⣴⠾⠻⢶⣦⠀
> > > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> > > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
> > > ⠈⠳⣄⠀⠀⠀⠀
> > >
> > >
>
> --
> Henning Follmann           | hfollm...@itcfollmann.com
>

Reply via email to