| Lists: | Postg스포츠 토토 결과SQL : Postg스포츠 토토 결과SQL 메일 링리스트 : 2019-03-13 이후 PGSQL-BUGS 04:54 |
|---|
| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | ashishpuneet(at)gmail(dot)com |
| Subject: | BUG #15690: PostgreSQL integration with AD via LDAP and special characters in the password |
| Date: | 2019-03-13 04:54:15 |
| Message-ID: | 15690-f6b1f8e17273170d@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | Postg스포츠 토토 결과SQL : Postg스포츠 토토 결과SQL 메일 링리스트 : 2019-03-13 이후 PGSQL-BUGS 04:54 |
The following bug has been logged on the website:
Bug reference: 15690
Logged by: ashish puneet
Email address: ashishpuneet(at)gmail(dot)com
PostgreSQL version: 9.6.6
Operating system: RHEL 7.4
Description:
Hi Team,
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.
Is it a know issue in PostgreSQL? Do we have any fix for this issue?
Thanks,
Ashish Puneet
| 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 |
| 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:
/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