seems like it expects auth.uid() to be a UUID wher...
# sqlb
bs-clerk
12/27/2021, 9:25 PMseems like it expects auth.uid() to be a UUID whereas mines set as text
c
chipilov
12/27/2021, 9:27 PMthe user id is, indeed, a UUID (you can check in the auth.users table)
chipilov
12/27/2021, 9:27 PMwhen you say "it expects" - what is "it"?
b
bs-clerk
12/27/2021, 9:29 PMhey thanks for your help. In the tutorial it has me setup this function
Copy code
create or replace function auth.user_id() returns text as $$
select nullif(current_setting('request.jwt.claim.userId', true), '')::text;
$$ language sql stable;auth.user_id() = user_idbs-clerk
12/27/2021, 9:30 PMHowever, I'm still getting"
Copy code
new row violates row-level security policy for table "todos"c
chipilov
12/27/2021, 9:30 PMok, I see, so you've created this function yourself (as instructed by the tutorial, that is)
b
bs-clerk
12/27/2021, 9:31 PMYup, and im having trouble debugging. everything looks like it's being sent up correctly, but i cant see if supabase is running that function, if the JWT is incorrectly setup, etc.
c
chipilov
12/27/2021, 9:31 PMwhat version of Postgres is your project using?
chipilov
12/27/2021, 9:32 PMit seems that this article uses a way to access the user id claim in a way that, as far as I know, is NOT compatible with Postgres 14 (Supabase recently updated to Postgres 14 for new projects)
b
bs-clerk
12/27/2021, 9:32 PMdo you know where i can find that info?
bs-clerk
12/27/2021, 9:32 PMahh gotcha. That sounds like its it
c
chipilov
12/27/2021, 9:32 PMrun this
chipilov
12/27/2021, 9:32 PMSELECT version();
b
bs-clerk
12/27/2021, 9:33 PMyup. im on 14.1
c
chipilov
12/27/2021, 9:34 PMok, in that case, I think you need to use the following:
chipilov
12/27/2021, 9:35 PMcurrent_setting('request.jwt.claims', true)::jsonb ->> 'sub'...not sure why the tutorial is using a 'userId' claim, I think the claim for the user id is 'sub'...in fact, I am not sure why the tutorial suggest to create a new function given that one already exists for exactly this purpose
chipilov
12/27/2021, 9:36 PMGiven that this is your own function, you can modify it by logging inside it and then you can see the log in the dashboard (Settings -> logs -> Database) - just make sure to log at WARNING level, otherwise it will NOT show up (by log, I mean to use the RAISE statement)
b
bs-clerk
12/27/2021, 9:37 PMThank you so much! This was really helpful. Do you know where theres documentation on this current_setting function, and the request jwt stuff?
It looks like "claim" was renamed to "claims", and we can no longer access the json via the dot notation?
c
chipilov
12/27/2021, 9:39 PMthe rename was documented in their latest release notes: https://github.com/supabase/supabase/releases
b
bs-clerk
12/27/2021, 9:39 PMah great. thanks a ton!
c
chipilov
12/27/2021, 9:41 PMyou can find the actual names of the claims at the bottom of this page: https://supabase.com/docs/learn/auth-deep-dive/auth-deep-dive-jwts (or, if you manually inspect the JWT contents using something like jwt.io)