Configure which feed a token can push packages to - introducing feed-scoped access tokens
Many development teams are making use of a continuous integration server like TeamCity, Jenkins or VSTS to build their projects and push generated NuGet, npm, Bower and VSIX packages to their MyGet feed. When having multiple feeds, it is a good practice to limit the feeds this access token/API key can push packages to, ensuring the surface area of the specific access token is limited to just the feeds the access token requires access to.
In short, scoped access tokens:
- Are a good security best-practice: use minimum required permissions for a specific operation
- Avoid services/users accidentally pushing packages by using read-only tokens where possible
- Allow pushing packages without the ability to get access to other packages on the feed (write-only)
New access tokens and existing access tokens can be scoped in terms of what they can do. We now let you to create read-only or write-only access tokens, optionally limiting write access to just one specific feed.
Next to scopes, the access token expiration date and time can also be specified, making it possible to create a time-limited access token that has to be recreated to continue having access to the feed.