Greetings,
* Chris Stephens (cstephen...@gmail.com) wrote:
> yes, shortly after i sent this out to the list, one of our security
> administrators suggested ldapscheme. I just tested and ldapurl works as
> well.
>
> the security admin explained it like this:
>
> "since we are using port 636 I kn
yes, shortly after i sent this out to the list, one of our security
administrators suggested ldapscheme. I just tested and ldapurl works as
well.
the security admin explained it like this:
"since we are using port 636 I know that it needs the TLS connection in
place before LDAP commands. starttl
Hi Chris,
> On 08. Jun, 2020, at 23:05, Chris Stephens wrote:
> posgresql 12
> centos 7
here: PostgreSQL 11.6 & 12.3, SLES 12 & 15
> hostsslall all 0.0.0.0/0 ldap
> ldapserver="ldaps://xxx" ldapbasedn="yyy" ldaptls=1
we use:
hostssl all all 0.0.0.0/0
On Tue, Jun 9, 2020 at 9:05 AM Chris Stephens wrote:
> hostsslall all 0.0.0.0/0 ldap
> ldapserver="ldaps://xxx" ldapbasedn="yyy" ldaptls=1
> does anyone know what might be causing "LDAP: Bad parameter to an ldap
> routine"
You probably want ldapurl="lda
posgresql 12
centos 7
i am trying to configure ldap authentication.
i have the following pg_hba.conf entry (server and basedn are correct but
not shown):
hostsslall all 0.0.0.0/0 ldap
ldapserver="ldaps://xxx" ldapbasedn="yyy" ldaptls=1
when i attempt to
