Skip to content
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

Use user.FullName in Oauth2 id_token response #32542

Merged
merged 1 commit into from
Nov 18, 2024

Conversation

baltitenger
Copy link
Contributor

This makes /login/oauth/authorize behave the same way as the /login/oauth/userinfo endpoint.

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Nov 17, 2024
@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 17, 2024
@github-actions github-actions bot added the modifies/go Pull requests that update Go code label Nov 17, 2024
@lunny
Copy link
Member

lunny commented Nov 17, 2024

But FullName maybe empty

@baltitenger
Copy link
Contributor Author

Then I guess the userinfo handler should be changed to work the same way, or both changed to use FullName with a fallback to Name

@baltitenger
Copy link
Contributor Author

Oh wtf, there's DisplayName and GetDisplayName... Would using DisplayName in both places be fine?

@pull-request-size pull-request-size bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Nov 17, 2024
@lunny
Copy link
Member

lunny commented Nov 17, 2024

I think both needs to be changed to use DisplayName, because it implemented a fallback if Fullname is empty.

@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Nov 18, 2024
@lunny lunny added the type/enhancement An improvement of existing functionality label Nov 18, 2024
@lunny lunny added this to the 1.23.0 milestone Nov 18, 2024
@wxiaoguang
Copy link
Contributor

Thank you for the PR!

It seems that DisplayName/GetDisplayName/FullName these names are too ambiguous .... I will try to make some improvements in this PR together to make them easier for contributors to understand

This makes `/login/oauth/authorize` behave the same way as the
`/login/oauth/userinfo` endpoint.
Copy link
Contributor

@wxiaoguang wxiaoguang left a comment

Choose a reason for hiding this comment

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

Maybe these function names could be refactored later, too complex ......

@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Nov 18, 2024
@wxiaoguang wxiaoguang removed their assignment Nov 18, 2024
@wxiaoguang wxiaoguang merged commit 5eb0ee4 into go-gitea:main Nov 18, 2024
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. modifies/go Pull requests that update Go code size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants