Repository navigation
feat: sync OIDC phone and picture claims - #124
Merged
qianmoQ merged 2 commits intoNov 3, 2026
Merged
Conversation
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
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.
Changelog category
Changelog entry
Affected version
Background and implementation
Applications using GrantForge as an OIDC provider need user phone numbers and avatar URLs when identities come from external providers such as Casdoor.
Persist phone and picture fields on local accounts and update them from upstream OIDC claims at sign-in. The phone claim is configurable (default
phonefor Casdoor);pictureuses the standard claim. Missing upstream values leave stored values unchanged. Add thephonescope to OAuth client configuration, returnphone_numberfor that scope andpictureforprofile, and update the console, API contract, migrations and documentation.Validation
phone_numberandpicture