Replies: 2 comments
-
|
The ClaimsUpd has little to do with the scopes and additional info you'd like. This is how it is usually used, and as you can see, it is a way to set custom attributed to the token For extra scope support, you should check #163 (just merged), allowing you to do what you need. Please note - this support in master only. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Is there any plan to release a new version with these changes soon? Just to mark this as answered Thank you |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I see in the ClaimsUpd function inside the auth Options, that the claims when signing with google are not being populated:
This is the response of the claims:
{ "name": "Iván RG", "id": "google_96*************e9dc45708106", "picture": "http://localhost:8000/avatar/" }I set the scopes of google sign in to provide user information but it's not being injected into the claims
Thank you
Beta Was this translation helpful? Give feedback.
All reactions