public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Jacob Champion <[email protected]>
To: [email protected] <[email protected]>
Cc: [email protected] <[email protected]>
Cc: [email protected] <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
Date: Wed, 2 Mar 2022 09:18:17 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<YhduhD/[email protected]>
<[email protected]>
<20220224171538.jbf2cxzmhiwuinp4@jrouhaud>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On 01.03.22 23:05, Jacob Champion wrote:
> On Tue, 2022-03-01 at 19:56 +0100, Peter Eisentraut wrote:
>> This patch contains no documentation. I'm having a hard time
>> understanding what the name "session_authn_id" is supposed to convey.
>> The comment for the Port.authn_id field says this is the "system
>> username", which sounds like a clearer terminology.
>
> "System username" may help from an internal development perspective,
> especially as it relates to pg_ident.conf, but I don't think that's
> likely to be a useful descriptor to an end user. (I don't think of a
> client certificate's Subject Distinguished Name as a "system
> username".) Does my attempt in v5 help?
Yeah, maybe there are better names. But I have no idea what the letter
combination "authn_id" is supposed to stand for. Is it an
"authentication identifier"? What does it identify? Maybe I'm missing
something here, but I don't find it clear.
view thread (10+ messages)
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 using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox