Skip to content

fix: use urlsafeB64Decode everywhere#627

Open
bshaffer wants to merge 4 commits intomainfrom
use-urlsafeb64encode
Open

fix: use urlsafeB64Decode everywhere#627
bshaffer wants to merge 4 commits intomainfrom
use-urlsafeb64encode

Conversation

@bshaffer
Copy link
Collaborator

@bshaffer bshaffer commented Mar 23, 2026

fixes #596

TODO

  • tests

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical issue where JWT keys might not be correctly interpreted due to inconsistencies in base64 decoding. By standardizing the key decoding process to use urlsafeB64Decode across relevant methods, the change enhances the reliability and security of JWT operations, ensuring that keys are always processed as intended.

Highlights

  • Key Decoding Consistency: Replaced base64_decode with self::urlsafeB64Decode in both the sign and verify methods to ensure consistent and correct decoding of keys, particularly for URL-safe base64 encoded strings.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly addresses the issue of decoding base64url-encoded EdDSA keys by switching to urlsafeB64Decode. My main feedback is about code maintainability and testing. I've added comments regarding duplicated code that should be refactored. Additionally, as noted in the PR description, tests are still pending. It is critical to add tests that verify this fix with base64url-encoded keys to prevent regressions.

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.

Issue with base64 decoding when using sodium_crypto

1 participant