Today I received a message from Supabase they will remove the use of the Anon Key.
If I check the request made by my project to the supabase /rest/v1 in the Log file, the request are made by the Anon key.
In the WeWeb Supabase Plugin I’ve tried to change the ‘Public Api Key’ to a new ‘Publishable Key’, but this results in a ‘Invalid Supabase Auth configuration.’-error in WeWeb.
How do I have to solve this issue, as the Anon key will be removed 8th of april, it’s quite urgent.
I was going to ask the same question here,
Seems like we have a month or so to make the changes
Is that something to change on the Supabase Plugin on Weweb ?
Thanks !
Same issue for me. Not sure how this will affect the auth process.
Same Issue here
Hey there 
I think we may not be using the anon key in projects where the plugin was configured with the “Connect Supabase” button but I’m not 100% sure. Let me check with the team and get back to you on that one
This does not affect normal Data API usage. Accessing data via
/rest/v1/your_tableor any client library will continue to work exactly as they do today.
