supabase-on-aws
supabase-on-aws copied to clipboard
Kong Authentication Request 401
Bug report
Describe the bug
On Friday, we had a working deployment of:
- public.ecr.aws/u3p7q2r8/kong:latest
- public.ecr.aws/supabase/gotrue:v2.69.2
- public.ecr.aws/supabase/postgrest:v11.1.0
Today, we get:
POST /auth/v1/token?grant_type=password HTTP/1.1" 401 in the Kong service
To Reproduce
We have deployed this in a terraform script. So we will likely need to stay high level in this issue.
Question
It seems like public.ecr.aws/u3p7q2r8/kong:latest is overwritten on publish. Did anything change that would make this incompatible with older versions of auth?
Is there perhaps any way to publish those old tags so we can stabilize the kong service?
Possible this is related to https://github.com/supabase-community/supabase-on-aws/commit/dee15837adc525971f6e4c08e7812211e402acd7
@mattrigg9 SOS
This was due to the renaming to "SUPABASE_ANON_KEY" from "ANON_KEY" and "SUPABASE_SERVICE_KEY"
This was due to the renaming to "SUPABASE_ANON_KEY" from "ANON_KEY" and "SUPABASE_SERVICE_KEY"
Wow!, You saved me! Thank you.