Removing GOTRUE_JWT_DEFAULT_GROUP_NAME results in: role "" does not exist
Obeyed opened this issue · comments
Bug report
- I confirm this is a bug with Supabase, not with my own application.
- I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
When GOTRUE_JWT_DEFAULT_GROUP_NAME=authenticated environment variable is not set then newly created users will have an empty role which breaks assumptions and results in role "" does not exist when postgrest and the database try to look up the role.
There is a deprecation warning regarding GOTRUE_JWT_DEFAULT_GROUP_NAME but removing it seems to break things. What's the correct solution if this environment variable is being removed in the near future?
To Reproduce
Don't set the GOTRUE_JWT_DEFAULT_GROUP_NAME=authenticated environment variable and invite a new user. The role column in the auth.users table will be empty.
Expected behavior
The role column is expected to be set otherwise
Additional context
Tried with docker image supabase/gotrue:v2.132.0
There is an old issue related to this that was closed by the auther, see: #948
Hey the notice is really about not using that with a custom role for now. It will be using authenticated or there'll be another way to define roles in the future.
I will fix the issue for removing it.