Ability to increase scopes without copy pasting a lot of code #81
mustafaakin
started this conversation in
Ideas
Replies: 1 comment
-
Allowing user-defined scores in Params won't solve the problem by itself. There are a few other things to be aware of:
Generally speaking, the decision to limit the scope to just a necessary minimum was a deliberate part of the design, and the goal was to minimize the info auth layer can access and pass. I have some use cases with post-auth "Registration" and this seems to be the right place to ask the user for the email and anything else. This info can be stored separately and populated into token's attributes as a part of user-defined If you can figure a simple and non-intrusive way to support extra scopes we can discuss it and, maybe, allow such customization. |
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
-
Since the current scopes are limited to name, id and avatar, adding an email scope requires copying & pasting a lot of code for each provider, but of course I can be wrong.
auth.go:
Using this feels a lot verbose, is this a good idea to allow scopes as a parameter?
Beta Was this translation helpful? Give feedback.
All reactions