Multiple API Keys

Multiple API Keys

Problem

Currently, NuGet.org users can only create a Single API key for all their projects. For large GitHub organizations, it is nessecary that multiple API keys be created that be scoped to specific actions and packages to prevent a single leak from compromising all the packages.

Who is the customer?

Who is the customer that is running into the problem. Which customers would dance for joy and donate to save the space unicorns foundation on getting this feature. Customers here could be individuals, nuget customer segments (package authors, consumers), enterprises, partners within Microsoft, external partners etc...

Evidence

What is the evidence that behaves us to act? Evidence can be impassioned tweets or mails, mile long conversations in issues, rants on blogs, sweet sweet data from telemetry!!! If you can show pain, you can rally the troops.

Solution

Detailed explanation of the solution. The more pictures/code snippets based on the feature the merrier. Pictures keep folks awake when reading specs.