Re: Proposal: Role Sandboxing for Secure Impersonation
От | Michał Kłeczek |
---|---|
Тема | Re: Proposal: Role Sandboxing for Secure Impersonation |
Дата | |
Msg-id | 89B3C4BA-60F0-4A73-ADAF-D8C89FBD563F@kleczek.org обсуждение исходный текст |
Ответ на | Re: Proposal: Role Sandboxing for Secure Impersonation (Eric Hanson <eric@aquameta.com>) |
Ответы |
Re: Proposal: Role Sandboxing for Secure Impersonation
|
Список | pgsql-hackers |
On 4 Dec 2024, at 17:13, Eric Hanson <eric@aquameta.com> wrote:On Mon, Dec 2, 2024 at 10:31 AM Wolfgang Walther <walther@technowledgy.de> wrote:Eric Hanson:
> a) Transaction ("local") Sandbox:
> - SET LOCAL ROLE alice NO RESET;
> - SET LOCAL ROLE alice WITHOUT RESET;
[snip]
> c) "Guarded" Transaction/Session
> - SET [LOCAL] ROLE alice GUARDED BY reset_token;
> - RESET ROLE WITH TOKEN reset_token;
These are preferable options for PostgREST (at least as long as JWT based impersonation is implemented in Postgres).
>
> Guarded sandboxes are nice because the session can also exit the sandbox
> if it has the token.
d) SET [LOCAL] ROLE alice WITH <password>;
PostgREST does not know alice's password as it performs JWT based authentication.
Regards
—
Michal
В списке pgsql-hackers по дате отправления: