From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jacob Champion <jchampion(at)timescale(dot)com>, "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: SYSTEM_USER reserved word implementation |
Date: | 2022-06-22 16:32:38 |
Message-ID: | 8dd72a01-a76b-8ebf-d9e7-f7d21dab0425@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/22/22 12:28, Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>> On 6/22/22 11:52, Tom Lane wrote:
>>> I think a case could be made for ONLY returning non-null when authn_id
>>> represents some externally-verified identifier (OS user ID gotten via
>>> peer identification, Kerberos principal, etc).
>
>> But -1 on that.
>
>> I think any time we have a non-null authn_id we should expose it. Are
>> there examples of cases when we have authn_id but for some reason don't
>> trust the value of it?
>
> I'm more concerned about whether we have a consistent story about what
> SYSTEM_USER means (another way of saying "what type is it"). If it's
> just the same as SESSION_USER it doesn't seem like we've added much.
>
> Maybe, instead of just being the raw user identifier, it should be
> something like "auth_method:user_identifier" so that one can tell
> what the identifier actually is and how it was verified.
Oh, that's an interesting thought -- I like that.
--
Joe Conway
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jacob Champion | 2022-06-22 16:48:08 | Re: SYSTEM_USER reserved word implementation |
Previous Message | Tom Lane | 2022-06-22 16:28:43 | Re: SYSTEM_USER reserved word implementation |