Skip to content

Conversation

@sweatybridge
Copy link
Contributor

@sweatybridge sweatybridge commented Jan 7, 2026

What kind of change does this PR introduce?

Bug fix #4614

What is the new behavior?

Initializes default signing key for curl http://127.0.0.1:54321/auth/v1/.well-known/jwks.json

Additional context

supersedes #4662

@sweatybridge sweatybridge requested a review from a team as a code owner January 7, 2026 02:41
@coveralls
Copy link

coveralls commented Jan 7, 2026

Pull Request Test Coverage Report for Build 20769557627

Details

  • 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
  • 5 unchanged lines in 1 file lost coverage.
  • Overall coverage increased (+0.008%) to 56.022%

Files with Coverage Reduction New Missed Lines %
internal/gen/keys/keys.go 5 12.9%
Totals Coverage Status
Change from base Build 20750278232: 0.008%
Covered Lines: 6847
Relevant Lines: 12222

💛 - Coveralls

@sweatybridge sweatybridge changed the title fix: generate default signing key fix: use asymmetric signing key by default Jan 7, 2026
@sweatybridge sweatybridge merged commit 85df1cc into develop Jan 7, 2026
12 checks passed
@sweatybridge sweatybridge deleted the dyn-key branch January 7, 2026 03:52
@mateuszbasiak
Copy link

mateuszbasiak commented Jan 7, 2026

Hi!
In most recent version of Supabase CLI (2.71.1) including these changes I started to encounter following error during npx supabase db reset:

Error status 400: {"statusCode":"403","error":"Unauthorized","message":"Key for the ES256 algorithm must be one of type CryptoKey, KeyObject, or JSON Web Key. Received an instance of Uint8Array"}

I tried running the same command in previous version as well (2.71.0) and it seems to work fine for without any issues.

Is this error related to these changes? Is there anything I could do to avoid this error?

@sweatybridge
Copy link
Contributor Author

It's a bug that I missed. I've opened a PR to address it in v2.71.2. Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

JWKS Endpoint Returns Empty Key Set for Local Supabase

4 participants