Repository navigation
fix(auth): Normalize client_sig and callerSig to SHA-1 hex digest - #262
Merged
LisoUseInAIKyrios merged 1 commit intoSep 13, 2026
Merged
Conversation
zeldrisho
marked this pull request as ready for review
September 11, 2026 10:41
LisoUseInAIKyrios
changed the title
|
Thanks for the help. |
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.
While integrating a separate custom Zalo patch maintained in Zeldris Patches, I found that Google Drive login could not acquire an OAuth token with microG-RE. This prevented Zalo’s image sync and backup/restore flow from working. Zalo is the reproduction case only; this PR contains no Zalo-specific changes.
The auth request was sending the certificate’s raw DER encoding as hexadecimal in
client_sigandcallerSig, while the endpoint expects the developer-console certificate SHA-1 fingerprint. That mismatch causedUNREGISTERED_ON_API_CONSOLE.This change normalizes both fields immediately before the auth request: existing 40-character SHA-1 values are preserved in lowercase, while DER-encoded certificate hex is decoded and hashed to a lowercase 40-character SHA-1 digest. The separate Zalo integration now completes Google Drive OAuth and backup/restore successfully, and existing integrations such as patched YouTube OAuth continue to work.