This project is read-only.

API keys should not be limited to GUIDs


As the title states, API keys can be anything. Not just GUIDs. I understand that you use a regex pattern to distinguish between file paths and keys, but you can do better than that. Add another activity variable to the workflow if you have to. Whatever it takes, let me use API keys that are not GUIDs.


dimonbut wrote Sep 15, 2014 at 9:26 PM

Proget use future when we can provide user & pass not apikey!
We want to use it!

wrote Sep 24, 2014 at 5:22 PM