Skip to content

fix(auth): preserve padded auth cookie values - #224

Merged
ralyodio merged 1 commit into
profullstack:masterfrom
aiirvizionz:clientkit/auth-cookie-preserve-padding
Aug 1, 2026
Merged

fix(auth): preserve padded auth cookie values#224
ralyodio merged 1 commit into
profullstack:masterfrom
aiirvizionz:clientkit/auth-cookie-preserve-padding

Conversation

@aiirvizionz

Copy link
Copy Markdown
Contributor

The public-key auth endpoints parsed cookies with split('=') and discarded everything after the first equals sign. Supabase base64 auth cookie values can include padding, so valid sessions were rejected when padding was present.

This patch:

  • preserves the complete cookie value after the first separator in both public-key endpoints
  • adds focused coverage for padded base64 auth cookies to the single-key and all-keys routes
  • keeps the existing authentication and service-role boundaries unchanged

Validation:

  • route.test.js and all/route.test.js: 4 tests passed with Vitest 4.1.8

@ralyodio
ralyodio merged commit bfd8053 into profullstack:master Aug 1, 2026
8 checks passed
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.

2 participants