-
Notifications
You must be signed in to change notification settings - Fork 449
fix(shared): Generate publishable keys with unpadded Base64 encoding to match backend output #8400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| '@clerk/shared': patch | ||
| --- | ||
|
|
||
| Generate publishable keys with unpadded Base64 encoding to match backend output. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: clerk/javascript
Length of output: 1057
🏁 Script executed:
Repository: clerk/javascript
Length of output: 4722
🏁 Script executed:
cat -n packages/shared/src/keys.ts | tail -n +100Repository: clerk/javascript
Length of output: 8694
🏁 Script executed:
Repository: clerk/javascript
Length of output: 325
🏁 Script executed:
Repository: clerk/javascript
Length of output: 11820
🏁 Script executed:
Repository: clerk/javascript
Length of output: 583
🏁 Script executed:
Repository: clerk/javascript
Length of output: 765
Critical: Unpadded Base64 keys will fail in browser environments.
Line 43 strips all Base64 padding via
.replace(/=+$/, ''), butisomorphicAtobpasses the unpadded string directly to browseratob(), which requires length to be a multiple of 4. Some keys (e.g., those with decoded length not divisible by 4) will throw in browsers—parsePublishableKey/isPublishableKey will fail for valid keys generated by buildPublishableKey.Tests pass in Node.js because
Buffer.from()accepts unpadded Base64, but browseratob()is stricter. Either restore padding before decode or do not strip padding on encode.🤖 Prompt for AI Agents