Re: DEFINER / INVOKER conundrum

Поиск
Список
Период
Сортировка
От walther@technowledgy.de
Тема Re: DEFINER / INVOKER conundrum
Дата
Msg-id f82f70fd-665f-6384-5e8a-987ab9e640d3@technowledgy.de
обсуждение исходный текст
Ответ на Re: DEFINER / INVOKER conundrum  (Erik Wienhold <ewie@ewie.name>)
Ответы Re: DEFINER / INVOKER conundrum  (Erik Wienhold <ewie@ewie.name>)
Список pgsql-general
Erik Wienhold:
> A single DEFINER function works if you capture current_user with a parameter
> and default value.  Let's call it claimed_role.  Use pg_has_role[0] to check
> that session_user has the privilege for claimed_role (in case the function is
> called with an explicit value), otherwise raise an exception.
> 
> Connect as postgres:
> 
>     CREATE FUNCTION f(claimed_role text default current_user)
>       RETURNS TABLE (claimed_role text, curr_user text, sess_user text)
>       SECURITY DEFINER
>       LANGUAGE sql
>       $$ SELECT claimed_role, current_user, session_user $$;

For me, checking whether session_user has the privilege for claimed_role 
is not enough, so I add a DOMAIN to the mix:

CREATE DOMAIN current_user_only AS NAME CHECK (VALUE = CURRENT_USER);

CREATE FUNCTION f(calling_user current_user_only DEFAULT CURRENT_USER)
...
SECURITY DEFINER;

This works, because the domain check is evaluated in the calling context.

Best,

Wolfgang



В списке pgsql-general по дате отправления:

Предыдущее
От: jian he
Дата:
Сообщение: Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
Следующее
От: Erik Wienhold
Дата:
Сообщение: Re: DEFINER / INVOKER conundrum