Yes, I'm sorry I should have been more specific in this regard however at the time of opening the ticket I wasnt properly informed and thus wasn't specific.
The issue is in relation to role impersonation. Given:
```
-- This file contains the definition of the applications specific roles
-- the roles defined here should not be made owners of database entities (tables/views/...)
\echo # Loading roles
-- the role used by postgrest to connect to the database
-- notice how this role does not have any privileges attached specifically to it
-- it can only switch to other roles
drop role if exists authenticator;
create role authenticator with
login
noinherit
password 'password1234blahblah';
-- this is an application level role
-- requests that are not authenticated will be executed with this role's privileges
drop role if exists anonymous;
create role anonymous;
grant anonymous to authenticator;
```
I'm not able to get the authenticator role to successfully switch/impersonate an anonymous role despite the above and given that the db uri uses the authenticator/password1234blahblah combo
In logs I get `ERROR: permission denied to set role "anonymous"`
Everything however works as expected if for example I use postgres/postgresPassword uri and with `grant anonymous to postgres` instead of the last line as shown above;
Is there some specific configuration settings that needs to be enables or adjusted to enable the above to function as expected and without using the postgres admin role specifically?