fix(cli): decode Go keyring tokens#5406
Merged
Merged
Conversation
Coly010
approved these changes
Jun 1, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changed
Decode
go-keyring-base64:wrapped access tokens when reading from the OS keyring in both the legacy and next CLI credential layers.Why
The Go keyring backend can store the real
sbp_...access token inside ago-keyring-base64:wrapper. The TypeScript credential readers were validating and using the raw wrapped value, so legacy Management API commands such assupabase secrets setfailed with an invalid access token format error even though the decoded token was valid.Notes for reviewers
The normalization happens at the keyring-read boundary so existing validation continues to run against the actual token value, not the storage representation.