Skip to content

new row violates row-level security policy for table "projects" #163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rayamajhii opened this issue Apr 27, 2025 · 4 comments
Open

new row violates row-level security policy for table "projects" #163

rayamajhii opened this issue Apr 27, 2025 · 4 comments

Comments

@rayamajhii
Copy link

Fronted:

Image

Backed:
Image

While trying to use it:
Image

Supabase:
Image

Notes in Supebase: To temporary fix this issue I removed "Row-Level-Security" on project, thinking anyone will be able to change this database. How ever it didn't work. Same issue encountered.

Maybe my Supabase set up is not working but everything looks fine. What is my issue. using linux arch

@cezary-klauza
Copy link

This issue means that you didn't add policy to the "projects" table, or policies which already exist doesn't allow to use required methods

@rayamajhii
Copy link
Author

Image

This is my first time ever dealing with database. I just learned that what is Supabase i kept seeing firebase while doing appsec but i never knew its job until today.

I understand that this Insert MEthord must return rows, and its because of that i encountered error. But IDK what should be the quarry could you please guide me here.

@rayamajhii
Copy link
Author

@cezary-klauza please ! help me

@leovdn
Copy link

leovdn commented Apr 27, 2025

It believe the wat to disable the Row Level Security you must go to Authentication > Policies > Select your schema (basejump) and click on Disable RLS for the desired row. If needed you could do the same for the public schema

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants