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

bug: Profile scopes not available #137

Open
NhProGamer opened this issue Oct 15, 2024 · 1 comment
Open

bug: Profile scopes not available #137

NhProGamer opened this issue Oct 15, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@NhProGamer
Copy link

NhProGamer commented Oct 15, 2024

Describe the bug

When you has the default webserver gin code and when the logged user has attributes like family_name, the server does not seems to show that value, when i change the struct UserInfoResponse and i add
FamilyName string json:"family_name" the server send me the attribute

Expected behavior

The server should correctly send me that info

How to reproduce?

Use the default golang example gin server, login with a user that have profile attributes like that
{
"familyName": "John",
"givenName": "Doe,
"nickname": "NhPro"
}

Context

  • [ X ] Self-hosted, Logto version = latest
    • [ X ] Container (Docker image)
    • Lib version 1.0.6

image

@NhProGamer NhProGamer added the bug Something isn't working label Oct 15, 2024
@NhProGamer
Copy link
Author

NhProGamer commented Oct 15, 2024

The documentation said: Other standard claims include family_name, given_name, middle_name, nickname, preferred_username, profile, website, gender, birthdate, zoneinfo, and locale will be also included in the profile scope without the need for requesting the userinfo endpoint. A difference compared to the claims above is that these claims will only be returned when their values are not empty, while the claims above will return null if the values are empty. BUT it dodn't work at all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

1 participant