Re: Interest in a SECURITY DEFINER function current_user stack access mechanism?

From: Nico Williams <nico(at)cryptonector(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Interest in a SECURITY DEFINER function current_user stack access mechanism?
Date: 2017-10-18 20:15:35
Message-ID: 20171018201534.GB4496@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alternatively, a way to get at the OuterUserId? Or the outer-most
current_user in the function stack?

I should explain why I need this: for audit functionality where I want
the triggers' procedures to be SECURITY DEFINER so only they can write
to audit tables and such, but I want them to see the current_user of the
*caller*, rather than current_user being the DEFINER's name.

Nico
--

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nico Williams 2017-10-18 20:26:50 Re: Interest in a SECURITY DEFINER function current_user stack access mechanism?
Previous Message Pavel Stehule 2017-10-18 20:15:01 Re: Interest in a SECURITY DEFINER function current_user stack access mechanism?