Re: BUG #15690: PostgreSQL integration with AD via LDAP and special characters in the password

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: ashishpuneet(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15690: PostgreSQL integration with AD via LDAP and special characters in the password
Date: 2019-03-18 04:33:56
Message-ID: 20190318043356.GZ6197@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Greetings,

* PG Bug reporting form (noreply(at)postgresql(dot)org) wrote:
> PostgreSQL version: 9.6.6

You should really upgrade to the most recent 9.6 version of PostgreSQL.

> We are trying to integrate PostgreSQL (9.6.6) with AD (Active directory)
> using LDAP and facing issues with integration and it seems that issue is
> because of the special characters that has been used in the password.

Can you be more specific regarding exactly what you're seeing? What
does "special characters" here mean, what's happening?

> Is it a know issue in PostgreSQL? Do we have any fix for this issue?

You might want to consider using Kerberos when integrating with an AD
environment from PostgreSQL, which would certainly avoid this issue.
You can see the PostgreSQL documentation for that here:

https://www.postgresql.org/docs/current/gssapi-auth.html

and I wrote up a blog post to try and help make it easier for people
which covers the Windows AD setup side of things and how you go about
actually getting a keytab and such here:

https://info.crunchydata.com/blog/windows-active-directory-postgresql-gssapi-kerberos-authentication

Thanks!

Stephen

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomasz Szypowski 2019-03-18 05:01:54 pg_upgrade
Previous Message 小威 2019-03-18 04:02:13 Re: BUG #15696: year field of interval type is not rounded to nearest integer