| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: PostgreSQL 18 Beta 1 release announcement draft |
| Date: | 2025-05-07 21:45:04 |
| Message-ID: | edf5c89c-8766-4a7f-b8f7-3f8a4ad9f7f1@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/7/25 5:16 PM, Jacob Champion wrote:
> On Tue, May 6, 2025 at 8:46 PM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>> Here's the next update
>
> Thanks!
>
>> PostgreSQL 18 introduces `oauth` authentication, which people can create extensions that support OAuth 2.0 based authentication mechanisms that PostgreSQL can authenticate with.
>
> Suggested alternative: "PostgreSQL 18 introduces `oauth`
> authentication, which lets the client retrieve OAuth 2.0 tokens and
> allows people to create server extensions that authenticate users with
> those tokens."
I did a double take on the current sentence, and revised it to:
==
PostgreSQL 18 introduces `oauth` authentication, which lets users
authenticate using OAuth 2.0 mechanisms supported through PostgreSQL
extensions.
==
I don't know how much we want to get into the back-and-forth flow in the
announcement itself, since it's more about raising awareness that this
exists, and then people can read the docs to find out more.
Thanks!
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2025-05-07 21:52:27 | Re: PostgreSQL 18 Beta 1 release announcement draft |
| Previous Message | Jonathan S. Katz | 2025-05-07 21:39:40 | Re: PostgreSQL 18 Beta 1 release announcement draft |