fix: defaults to legacy anon key

[sweatybridge]

What kind of change does this PR introduce?

fixes: #4751
follow up #4688

What is the new behavior?

Keep legacy anon and service_role keys around unless user explicitly enables custom signing key.

Additional context

supersedes #4752

[coveralls]

Pull Request Test Coverage Report for Build 21507572784

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 10 unchanged lines in 3 files lost coverage.
• Overall coverage decreased (-0.05%) to 55.437%

---

Files with Coverage Reduction	New Missed Lines	%
internal/storage/rm/rm.go	2	80.61%
internal/debug/postgres.go	3	66.09%
internal/gen/keys/keys.go	5	12.9%

Totals
Change from base Build 21507125506:	-0.05%
Covered Lines:	7107
Relevant Lines:	12820

---

💛 - Coveralls

[mateuszbasiak]

Hello!
After this change I started to encounter following error while calling supabase.auth.admin using secret (sb_secret_) key from supabase status:

[AuthApiError: invalid JWT: unable to parse or verify signature, token signature is invalid: signing method HS256 is invalid]

While using previous version of CI I'm able to avoid this issue. I didn't configure custom signing key. Is this error expected? Is there anything I could do to avoid it besides switching fully to asymmetric keys?

[sweatybridge]

Sorry this became a bit of a whack a mole. There's another fix that we need to land #4781

I will test more before merging.

[sweatybridge]

Could you give v2.74.4 a try? It should accept sb_secret_ key even if you are still using legacy api keys.

[mateuszbasiak]

@sweatybridge Seems to be working now. Thank you for quick action