search

cberio / google-api-java-client

Automatically exported from code.google.com/p/google-api-java-client
0 stars 0 forks source link

Only require a context-sensitive subset of permissions for Service Accounts #917

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
External references, such as a standards document, or specification?

https://developers.google.com/android-publisher/edits/

Java environments (e.g. Java 6, Android 2.3, App Engine, or All)?

All

Please describe the feature requested.

The current way of editing a Play Store entry with the Google Play Developer 
API requires an admin to grant four permissions simultaneously:

* Edit store listing, pricing & distribution
* Manage Production APKs
* Manage Alpha & Beta APKs
* Manage Alpha & Beta Users

as those resources MAY be changed by the incoming Edit. However, it would be 
much more secure to only require those permissions that are actually touched by 
the incoming Edit. For example, if we know we only ever upload to the alpha 
track we could create a service account with only that one permission. 
Especially, since there already are permissions like that.

Original issue reported on code.google.com by hurlin...@googlemail.com on 14 Nov 2014 at 6:54

GoogleCodeExporter commented 9 years ago 
+1 for this. We have an app that has 100m+ installs, so granting access to the 
Play Store in any form is done with extreme caution.

Using our case as a specific example:

We plan to use a separate listing on the play store for distributing internal 
betas within the company. This would only exist on that listing's alpha 
channel, and we would manage alpha user access to it via the console only. 

Ideally, we would like to only have to grant permission to upload alpha/beta 
builds and to update listings. Due to this broad requirement for the API 
however, we also *have* to give it permission to upload production builds and 
manage alpha/beta users.

Original comment by zac.swe...@gmail.com on 14 Nov 2014 at 9:56

GoogleCodeExporter commented 9 years ago 
Thanks for the feedback. We'll try to get this resolved at our earliest.

Original comment by wonder...@google.com on 20 Nov 2014 at 6:56

GoogleCodeExporter commented 9 years ago 
Here's the response from Google Play Developer Support, I hope this helps.

Thanks for contacting Google Play Developer Support.

Currently, we require all API users accounts to have both "Manage Alpha & Beta 
APKs" and "Manage Production APKs" permissions in order to upload and commit 
(publish) APKs through the API to any track (Alpha, Beta or Production). We are 
aware this enables API users to publish APKs to Production and are currently 
working to improve user access behavior. I apologize for any inconvenience this 
may cause.

As a workaround, if you wish to restrict user access to publishing only Alpha 
and Beta APKs, we recommend using a build server with a service account, which 
will allow you to control access to what can be pushed to the build server.

If you have any further questions, please let me know.

Original comment by wonder...@google.com on 29 Dec 2014 at 4:53

GoogleCodeExporter commented 9 years ago 
Thank you for the update and for looking into it. The build server is a decent 
solution, but not a particularly convenient one. Hopefully they change this 
requirement soon!

Original comment by zac.swe...@gmail.com on 29 Dec 2014 at 5:27

GoogleCodeExporter commented 9 years ago

Original comment by wonder...@google.com on 29 Dec 2014 at 7:07

GoogleCodeExporter commented 9 years ago 
Just a FYI, you can contact the Developer Console Help Center located at 
https://support.google.com/googleplay/android-developer/?hl=en#topic=3450769 
for Google Play Developer API related questions. Engineers from that team will 
assist you directly.

Original comment by wonder...@google.com on 2 Jan 2015 at 3:07