Why does Appveyor need read AND write permissions
When I went to setup an account via oauth, appveyor requested read and write access to ALL of my public and private repos, even though I am signing up for an Open Source account.
Why is write access required? Why would appveyor need these permissions to all repos both public and private?
Hesitant to sign up until I understand why these requirements for permissions above and beyond what they should need are met. Open Source means public READ access which is not a problem, but giving READ & WRITE privs to ALL repos (public or private) is over reaching.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 09 Apr, 2015 01:33 AM
There are two options when you are authorizing:
You can choose "public repositories".
2 Posted by Jeff Hinrichs on 09 Apr, 2015 02:24 AM
Starting here: https://ci.appveyor.com/signup
I select Open Source
Then click on BitBucket and the oauth starts and I get:
Confirm access to your account
AppVeyor CI <http://www.appveyor.com/> is requesting read and write access
to your public and private repositories.
Grant access Cancel <https://bitbucket.org/>
I am not seeing any option to choose.
Best,
Jeff
Support Staff 3 Posted by Feodor Fitsner on 09 Apr, 2015 02:45 AM
Oh, it's BitBucket. Unfortunately, BitBucket does not have OAuth scopes: https://confluence.atlassian.com/display/BITBUCKET/OAuth+FAQ#OAuthF...?
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:55 AM.