Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1elr0f-0005jD-Nh for pgsql-admin@arkaria.postgresql.org; Wed, 14 Feb 2018 06:57:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1elr0e-0007vR-L0 for pgsql-admin@arkaria.postgresql.org; Wed, 14 Feb 2018 06:57:40 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1elr0d-0007vG-RO for pgsql-admin@lists.postgresql.org; Wed, 14 Feb 2018 06:57:40 +0000 Received: from mail-oln040092068023.outbound.protection.outlook.com ([40.92.68.23] helo=EUR02-HE1-obe.outbound.protection.outlook.com) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1elr0Z-0001Kx-Q5 for pgsql-admin@postgresql.org; Wed, 14 Feb 2018 06:57:38 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=arIzCwSBVXGFiDgsPPmVSvefLdU8aVebDfK2V8BWoTU=; b=aZ0NBEuc2wwxtGsre1hAg09phxPN+xtOo9NgowO6WjfP/z9bnn6s1tEsfSXEvdyPIoahSSEgFwiPIs9jF7P8Ds/GAj7KRwi28rcgJAc+MR9ThsBHZUOhepzJyv2rHVSGpaIcsQ4o9qU0P0bNQU9mJCsUgra8fphmlGIfpVD1GIEt8OMyI6VQPXI/qcaFd29umhaf49S9bhBd9v5HA1+5lEc7eWEBwOseU1LA2rrBPpfY0px9Ny/jVQ+riirrkgfJV7GFz8xphld6PDMWQ8slK3+c+fF4voftVSNK3iF+KABPvJ1m0k7Ac+VuCT8+72wkqhab5Pgi4fhX4TdtPYoRXQ== Received: from VE1EUR02FT058.eop-EUR02.prod.protection.outlook.com (10.152.12.51) by VE1EUR02HT051.eop-EUR02.prod.protection.outlook.com (10.152.13.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.485.12; Wed, 14 Feb 2018 06:57:32 +0000 Received: from DB6PR10MB1846.EURPRD10.PROD.OUTLOOK.COM (10.152.12.55) by VE1EUR02FT058.mail.protection.outlook.com (10.152.13.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.485.12 via Frontend Transport; Wed, 14 Feb 2018 06:57:32 +0000 Received: from DB6PR10MB1846.EURPRD10.PROD.OUTLOOK.COM ([fe80::7d33:8af7:551c:e005]) by DB6PR10MB1846.EURPRD10.PROD.OUTLOOK.COM ([fe80::7d33:8af7:551c:e005%13]) with mapi id 15.20.0485.017; Wed, 14 Feb 2018 06:57:32 +0000 From: Sathesh S To: "pgsql-admin@postgresql.org" Subject: Disable /Suppress hostname checks while secured LDAP Thread-Topic: Disable /Suppress hostname checks while secured LDAP Thread-Index: AQHTpWEVjAhKGrLTvkKHTQrhGcGD1Q== Date: Wed, 14 Feb 2018 06:57:32 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:E48324D621BE089BA70EBCABA7C627242218A52FFE1FB43465370C0419C31FCA;UpperCasedChecksum:48DA979E680CCC436C83D71402031DDA83FCCECDA8BC3BF0D3F7A04F735816E9;SizeAsReceived:6931;Count:44 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [ZcSDdbnc45QkxEpnsUcfu9vEoLpACgtZ] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1;VE1EUR02HT051;6:m+ZmfVjaEI/f/WYd860NGhWIV1KXGavM2Pq0jdZgCYCqt8NJwAFU98JukHTkkFWkVN6tjZWwzrla0KBAQijKZ67DJjKphzPoWjAo3y6F9rE1R0hxRpDs4ms1IjIzuC2GlA1POLA5cdo3vfQBfUdXmI3P+3L8WCfQkOxDTOnPALa+t/PyzIkT8gBeBIwRRn5mute40wZi/UfvmiWN312iSqWuY7u2eAYAZGnAHlNwbwI6FAxgiO9PjfvXeDzq2imnckVCUIYUMK+0dtqlZcJ31b2gasH3fr0RJrUT/iDjX8uUuZ15j3shtdEamOT1W2b8ZdiWoGYMT0rQuouhsYZGRkpKNjI2sQaYAHC6q/MvLN0=;5:JofurBTqjlu1+aw9XPt+pLzm6trceqsF3861bbCsVUDfldxT+Er1+SvobpfczmvMXHYEoFFwavQ3LlnedIpCDykkntWMAWBgsLXY9du1t4Cp9riHJyuiNimnNkUrNsIpE3qfd25+FtiB2XOH0caWS5IMqLtic5ZYunXE7ufbfT8=;24:PuxZFRulD5+VMSwXxKwUyUpK/+jYy/K+SBwSI/Kt60XZH3b57ZyqQ/UC0z0nFNCQH5qCkNfKzRA394kbnOVSltInn0GmtDrH8qzzbYhW7hc=;7:KtSKT2k1AH8g/6pXlz26lu2FwM2jhBNzr7aKXvLArKtZiLBO2N+7LDqc2no6HvquoTi2xBOtfx5AH7afUahuvucWJgj0Z5MyPH8TTCe3UocXX9cXxVUAYeUrVIY+igX5R4xHS/j9I37QMsVSqI0OaRXG3dLP/zn9k/NsmOGHCjCHutKOFUpBoOTtiETyH6gAb10B8LGLZwfIKNkIEph7KnxvfaDH8Fja/RjVYt+EQQ+tkTBXjOTmeMGvmN6zo4bm x-incomingheadercount: 44 x-eopattributedmessage: 0 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(7020095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101448)(1601125374)(1701031045);SRVR:VE1EUR02HT051; x-ms-traffictypediagnostic: VE1EUR02HT051: x-ms-office365-filtering-correlation-id: 53c794de-b1d4-4436-ee34-08d573783876 x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(444000031);SRVR:VE1EUR02HT051;BCL:0;PCL:0;RULEID:;SRVR:VE1EUR02HT051; x-forefront-prvs: 0583A86C08 x-forefront-antispam-report: SFV:NSPM;SFS:(7070007)(98901004);DIR:OUT;SFP:1901;SCL:1;SRVR:VE1EUR02HT051;H:DB6PR10MB1846.EURPRD10.PROD.OUTLOOK.COM;FPR:;SPF:None;LANG:; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_DB6PR10MB1846529979DDF09DE728FE2D82F50DB6PR10MB1846EURP_" MIME-Version: 1.0 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-Network-Message-Id: 53c794de-b1d4-4436-ee34-08d573783876 X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2018 06:57:32.2131 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR02HT051 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --_000_DB6PR10MB1846529979DDF09DE728FE2D82F50DB6PR10MB1846EURP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello All, Is there a way to disable/suppress hostname checks in while using Secured L= DAP in postgreSQL for authentication. The issue what we have is that the LDAP certificate what we are using is wo= rking for fully qualified named of the domain but not when we use a direct = LDAP server in the pg_ba.conf file. For example: This works - ldapserver=3D"ldaps//dummy.company.com" This doesnt work - ldapserver=3D"server1.dummy.company.com" Our internal LDAP team says that we nees to disable/suppress the hostname c= hecking on the postgreSQL side for the 2nd option to work. Does anyone have an idea on how we can suppress hostnames check while using= Secured LDAP. Thanks , Sathesh --_000_DB6PR10MB1846529979DDF09DE728FE2D82F50DB6PR10MB1846EURP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hello All,

Is there a way to disable/suppress hostname checks in while using Secured L= DAP in postgreSQL for authentication.

The issue what we have is that the LDAP certificate what we are using is wo= rking for fully qualified named of the domain but not when we use a direct = LDAP server in the pg_ba.conf file.

For example:
This works - ldapserver=3D"ldaps//dummy.company.com"

This doesnt work - ldapserver=3D"server1.dummy.company.com"

Our internal LDAP team says that we nees to disable/suppress the hostname c= hecking on the postgreSQL side for the 2nd option to work.

Does anyone have an idea on how we can suppress hostnames check while using= Secured LDAP.

Thanks ,
Sathesh
--_000_DB6PR10MB1846529979DDF09DE728FE2D82F50DB6PR10MB1846EURP_--