Currently there are only two scopes for the API tokens, read-only and read-write, but this tokens are extremely dangerous as they affect all the resources in the account without restrictions. For example, create a million droplets or delete all of them.
It would be more desirable to have more control over the scope by choosing the resources it will operate on, i.e. droplets, volumes, floating IPs, etc. And a quota to limit their blast radius in the case of a security incident.
Are we getting something like this anytime?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
I agree it is absolutely a good idea and something that has been discussed internally. I am not aware if it is currently on the roadmap and would definitely encourage adding/voting for it on our uservoice site. Uservoice votes play a big role in what features are prioritized.
To be honest, this sounds is great idea. For now we are only limited with Read/Write privileges, maximum Droplet limit and 5000 request per hour which is pretty high.
Maybe @ryanpq can give us more insight on this, if he’s able to get more info. :D
In meanwhile, you can submit your idea on DigitalOcean’s UserVoice. :)
I’d like to ask the same questions as @CloudClam - seems like fine-grained API tokens are an industry standard by now, and it seems quite dangerous to keen any tokens in the wild that are very binary (you either get everything or nothing).
I found this post while looking for more fine-grained scopes. I want to use an API key to update a DNS record, and the thought of the same key being able to do everything makes me uneasy. Honestly I was surprised to see scopes limited to just
readandwriteas I usually feel Digital Ocean’s services are full-featured and modern. Hopefully more fine-grained scopes are considered soon.Any update on this ‘old’ post about restricting API token?
I notice the uservoice site is no longer available.