Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lKRZu-0001nu-Lt for pgsql-admin@arkaria.postgresql.org; Thu, 11 Mar 2021 20:06:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lKRZt-0002n2-KI for pgsql-admin@arkaria.postgresql.org; Thu, 11 Mar 2021 20:06:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lKRZt-0002lb-BD for pgsql-admin@lists.postgresql.org; Thu, 11 Mar 2021 20:06:37 +0000 Received: from hilly.subnetz.org ([2a01:4f8:221:1d05::2]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lKRZm-0003jW-J9 for pgsql-admin@lists.postgresql.org; Thu, 11 Mar 2021 20:06:35 +0000 Received: from mail.subnetz.org (xdsl-188-155-54-175.adslplus.ch [188.155.54.175]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) client-signature RSA-PSS (2048 bits)) (Client CN "holly.subnetz.org", Issuer "R3" (verified OK)) by hilly.subnetz.org (Postfix) with ESMTPS id BD7C820083AB for ; Thu, 11 Mar 2021 21:06:26 +0100 (CET) Received: from mother.subnetz.org (mother [192.168.5.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.subnetz.org (Postfix) with ESMTPS id 4DF7C103C4AE6 for ; Thu, 11 Mar 2021 21:06:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=subnetz.org; s=dkim; t=1615493186; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=vcUCNzLyA1M5XhXvdQGtIudmRO7niAY02i/PPRArnA4=; b=ezNo0xpaOEItvmywSci/cxVVdpAKg8v62M0XPzUGfl14/8NmcaKvxq3C5LusVkYemdgHo2 WEMW+9/XLQwi97QFrgPcDS4wIIWLm5nd4vtngZLo0r/8fcQIUMWLfRS1X/wINxyz+GNDAX 78RKrSZBc5UtNsUVpC8MyDBj3CiLimKEXeJqZAUd6+xN/2Nmmm9tfYqBI9PZcy6wX8CH/m jGrYcMXc7UPsv9XPUpIknSuyuV7N6YmBSfvMd/m9Dp+i9pB2DUiKDor9dUd7TMKyGWqlbk ti3ZcXqD00y4IEbdKJx6ArEYm6uWmMcaTeEKj8RPhe3hCpAs1ex2cwHXyJyPgg== Message-ID: Subject: applicable mapping for clientcert=verify-full From: Tilman Koschnick To: pgsql-admin@lists.postgresql.org Date: Thu, 11 Mar 2021 21:06:25 +0100 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, I'd like to combine password authentication with the clientcert=verify- full option. According to the documentation, this would enforce that the "cn ... matches the username or an applicable mapping". If I try to specify the mapping by setting the map= option, I get the following error: authentication option "map" is only valid for authentication methods ident, peer, gssapi, sspi, and cert How do I specify the applicable mapping in that case? Kind regards, Til