Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hOiOn-0000rW-CC for pgsql-general@arkaria.postgresql.org; Thu, 09 May 2019 12:43:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hOiOk-0003W2-RA for pgsql-general@arkaria.postgresql.org; Thu, 09 May 2019 12:43:42 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hOiOk-0003OI-3b for pgsql-general@lists.postgresql.org; Thu, 09 May 2019 12:43:42 +0000 Received: from mail-wm1-x343.google.com ([2a00:1450:4864:20::343]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hOiOh-00017C-Ji for pgsql-general@lists.postgresql.org; Thu, 09 May 2019 12:43:40 +0000 Received: by mail-wm1-x343.google.com with SMTP id f2so3036431wmj.3 for ; Thu, 09 May 2019 05:43:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=lWwSPHnEl7RjudQjPnJCxGhtB6Jr/q2GvLb1ghz1wq0=; b=1sTeQl4jRyIKr7eyTETgBaOK7qfyfGOAVvF6WchVtgiGgKQuqUNk/dr8edWR+P1Wb9 Rvjb2dhrllM8bShxq/XX1wOyLb56EWyM+1rAO3NN4nnyK6ZzKZZfrNwCynS7IfWDt43Y XBtfFSpheuQGB3GUEqgyGkJnMP/ZdDK5mkvitEbVJFWvR31tvB7dk5nvP4ZNjH9+y091 V3QXLqLdrxpW6SyPL9bqgBE++bGO61wicTsYjAbGb/lquHckyBLYp5oqfSNViWaUd5jW xpynaHbODNLHoR+og9VjLgYbVOTSpaJhDJPsKkID+SWuTrUj1TiqmdPfTd86Udb5cMiU Qc6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=lWwSPHnEl7RjudQjPnJCxGhtB6Jr/q2GvLb1ghz1wq0=; b=j63qnvD1feLET3Y8I71u7rn0tEj6cpuR+jqbrzNOrQgW2TbR28AGKzBf+cr+sgwyPI 4yqQaWhQ2+pcM2i6Wo5sX3dVD0FnwUNmH3bQKSx8zFbbmfaMPa4fLVa6Hz3m1umwlqE9 6o0eE9MCu3tLpa0g54IJFpE7Bq5HPCodpA91zyriCyY35B0v9qpNTFLnhpjjL7xXFx5C q8Bp8n1GOkck6mRmyxZXAgTlRkY+sThTJ+zVeiIMTLC8IDAw/0CjciorV6RclZW6APci G+X3/ZbTacE4RWf6fYcWf6wMkChtbksk6NNrO7aKCVsJhpChGgRRBDo6C1/QNTkb6TUp +epA== X-Gm-Message-State: APjAAAXZG3gTCoPOaSDwQJTpiZBn81WVhvCrkYQzCMbzLv+LAQq6cm2/ ExAt7RxB3IejR9TmxGhMjhZD3w== X-Google-Smtp-Source: APXvYqyci7miFLlDHuEJKtks1W5aCsUo3zxA14sJ2UltS9TComSaWwyi1kgkQzs6VknZo8XtSgYgNw== X-Received: by 2002:a7b:cb58:: with SMTP id v24mr2628813wmj.121.1557405817868; Thu, 09 May 2019 05:43:37 -0700 (PDT) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id g10sm2314360wrw.80.2019.05.09.05.43.23 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Thu, 09 May 2019 05:43:23 -0700 (PDT) Date: Thu, 9 May 2019 14:43:20 +0200 From: Tomas Vondra To: M Tarkeshwar Rao Cc: Laurenz Albe , pgsql-general , "'postgres-discuss@mailman.lmera.ericsson.se'" , Aashish Nagpaul Subject: Re: integrate Postgres Users Authentication with our own LDAP Server Message-ID: <20190509124320.ccwlfat7uv4iua4f@development> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716-1444-295967-dirty List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, May 09, 2019 at 07:11:24AM +0000, M Tarkeshwar Rao wrote: >We want to setup ldap authentication in pg_hba.conf, for Postgresql >users(other than postgres super user). > >We are getting issue with special characters by following steps given in >postgres documentation. It is not accepting any special characters as >special characters are mandatory in our use case. > >Can you please help us or have you any steps by which we can configure >any postgres with LDAP? Please don't cross-post - this is a fairly generic question, it has nothing to do with performance or development, so the right thing is to send it to pgsql-general. Likewise, it makes little sense to send questions to the "owner". I've removed the other lists from CC. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services