You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pgrst.jwt_secret in-database configuration can interpret a file path when it should not. For example:
create or replacefunctionpostgrest.pre_config()
returns void as $$
select set_config('pgrst.jwt_secret', '@/path/to/secret', true);
$$ language sql;
Right now, it reads the values inside /path/to/secret, but it should interpret the secret as is. That is, the secret should be the string "@/path/to/secret".
The text was updated successfully, but these errors were encountered:
I think @/does/not/exist when given via database configuration should be interpreted as a secret, not as a path. So a secret starting with @.
Agree, also mentioned here #3634 (comment). I'll change the title and description of the issue since the original one is no longer relevant.
laurenceisla
changed the title
PostgREST partially starts and does not return error when selecting an invalid file in pgrst.jwt_secret
The pgrst.jwt_secret in-database configuration should not interpret a file path
Jul 6, 2024
Description of issue
The
pgrst.jwt_secret
in-database configuration can interpret a file path when it should not. For example:Right now, it reads the values inside
/path/to/secret
, but it should interpret the secret as is. That is, the secret should be the string "@/path/to/secret".The text was updated successfully, but these errors were encountered: