pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: sujiplr@gmail.com
Subject: BUG #16234: LDAP Query
Date: Mon, 27 Jan 2020 14:55:53 +0000
Message-ID: <16234-7846cd633d16a812@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16234
Logged by:          Sujith kumar
Email address:      sujiplr@gmail.com
PostgreSQL version: 9.5.20
Operating system:   RHEL 7.7
Description:        

Hi Team,

I have a requirement to do authentication through LDAP, the LDAP query
should go to two different LDAP servers with dedicated binding users (
different for two LDAP servers) , if the user is not available in first LDAP
then it should check in second LDAP. But here as per hba file , it won't
work in this model ( If there is no successful search in first hope, it will
throw error). 

So we have to do multiple query in the LDAP query string, how we can do
this? 

Regards,
Sujith Kumar.S



view thread (4+ messages)  latest in thread

Message-ID: <16234-7846cd633d16a812@postgresql.org>
Permalink:  ../16234-7846cd633d16a812@postgresql.org/
Also on:    postgresql.org/message-id/16234-7846cd633d16a812@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, sujiplr@gmail.com
  Subject: Re: BUG #16234: LDAP Query
  In-Reply-To: <16234-7846cd633d16a812@postgresql.org>
  References: <16234-7846cd633d16a812@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox