Kong Authentication Request 401

[Jacobsolawetz]

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?

[Jacobsolawetz]

Possible this is related to dee1583

[Jacobsolawetz]

@mattrigg9 SOS

[Jacobsolawetz]

This was due to the renaming to "SUPABASE_ANON_KEY" from "ANON_KEY" and "SUPABASE_SERVICE_KEY"

[gimdongwoo]

This was due to the renaming to "SUPABASE_ANON_KEY" from "ANON_KEY" and "SUPABASE_SERVICE_KEY"

Wow!, You saved me! Thank you.