Re: [PATCH] Expose port->authn_id to extensions and triggers - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Expose port->authn_id to extensions and triggers
Date
Msg-id 98e600a9-77c3-970a-93df-fbd19b54c7cd@enterprisedb.com
Whole thread Raw
In response to Re: [PATCH] Expose port->authn_id to extensions and triggers  (Jacob Champion <pchampion@vmware.com>)
Responses Re: [PATCH] Expose port->authn_id to extensions and triggers
List pgsql-hackers
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.



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Add the replication origin name and commit-LSN to logical replication worker errcontext
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: pg_stop_backup() v2 incorrectly marked as proretset