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

scopes for github oauth #29

Open
memen45 opened this issue Sep 1, 2021 · 2 comments
Open

scopes for github oauth #29

memen45 opened this issue Sep 1, 2021 · 2 comments
Labels

Comments

@memen45
Copy link

memen45 commented Sep 1, 2021

+ '&scope=' + encodeURIComponent('user repo notifications')

In this line more access is requested compared to what is described in settings. Should it not be read:user user:email notifications instead to be more specific?

As mentioned in the "connected accounts" GitHub settings hint, you should check "read:user", "user:email" and "notifications" permissions.

Originally posted by @eneiluj in #18 (comment)

julien-nc pushed a commit that referenced this issue Sep 1, 2021
Signed-off-by: Julien Veyssier <eneiluj@posteo.net>
@julien-nc
Copy link
Member

Yes well, when using OAuth, we request more scopes than when using a personal token. It's not a big deal as the app never makes any action which require the user:follow permission.

Keep in mind that the instructions in the settings are for personal tokens and the line you mention is about the scopes that are required when getting a token via OAuth.

Did I understand your concern?

Anyway, for security reasons, let's limit the OAuth scopes as much as possible, you're right. it's done and pushed. It will be included in the next release.

@memen45
Copy link
Author

memen45 commented Sep 1, 2021

Yes, indeed, both scopes repo and user:follow are not used then, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants