to use the 389 server as my LDAP server. Ultimately I'm going to want
to use the 389 server as the LDAP server that works with Foreman.
I started down this road, hit a snag, and then, while trying to solve it
I ran into stuff that was EOD'd, deprecated, whatever. I'm getting lost.
Here's what I can do as of 1 July. My 389 server will act as an LDAP
server for the machine running the server -- that is, I can't get any clients
to refer to my 389 server (called fs) as the LDAP server. I was able
to do that when my server was openldap. Openldap is now... deprecated?
something like that. And Foreman seems to insist on the 389 server.
My clients are a mix of Centos 8 and Raspbian/R. Pi OS; both of which
use openldap stuff as their client -- AFAICT.
Okay, so after all that, what's my issue? All of my clients say this:
Code: Select all
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
but evidently authselect is not to be used under all circumstances(?).
Can/should I use authselect if I'm ultimately going to use Foreman?
If so, can someone direct me to an authselect tutorial? (I'm struggling
with the man page.)
In a sense I'm only trying to move my LDAP server from one machine
to another, but now it looks like my choice of server may conflict with