Re: Proposal: Save user's original authenticated identity for logging - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Proposal: Save user's original authenticated identity for logging
Date
Msg-id 20210201234013.GD27507@tamriel.snowman.net
Whole thread Raw
In response to Re: Proposal: Save user's original authenticated identity for logging  (Jacob Champion <pchampion@vmware.com>)
Responses Re: Proposal: Save user's original authenticated identity for logging
List pgsql-hackers
Greetings,

* Jacob Champion (pchampion@vmware.com) wrote:
> On Mon, 2021-02-01 at 18:01 -0500, Stephen Frost wrote:
> > Ok..  but what's 'go' mean here?  We already have views and such for GSS
> > and SSL, is the idea to add another view for LDAP and add in columns
> > that are returned by pg_stat_get_activity() which are then pulled out by
> > that view?  Or did you have something else in mind?
>
> Magnus suggested a function like pg_get_authenticated_identity(), which
> is what I was thinking of when I said that. I'm not too interested in
> an LDAP-specific view, and I don't think anyone so far has asked for
> that.
>
> My goal is to get this one single point of reference, for all of the
> auth backends. The LDAP mapping conversation is separate.

Presumably this would be the DN for SSL then..?  Not just the CN?  How
would the issuer DN be included?  And the serial?

Thanks,

Stephen

Attachment

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Typo in tablesync comment
Next
From: Tom Lane
Date:
Subject: Re: Should we make Bitmapsets a kind of Node?