Intranet-Level Nuget Private Channel: Setting Up Windows Embedded Security

Question

I’m thinking about setting up a Nuget feed at the intranet level (it’s assumed that it will use a group of teams in my company).
I briefly reviewed a few tutorials + related chapters in Pro Nuget , however, so far I still have a question:

• How to make an integrated security system for working in a private feed smoothly and configure access rights for a private Nuget feed (for example, provide everyone with the opportunity to receive packages, but provide access to only a few users / user groups);
• How to allow developers to send packets to a private channel without api key ?
• How to save developers from such a stupid mistake as transferring a package to a public channel? Is this enough to not configure the api key for the default public feed?

Has anyone come across one of these cases? Any hints are welcome.

Thanks!

Answer 1

I have not tried this so far, but following these instructions: http://docs.nuget.org/docs/creating-packages/hosting-your-own-nuget-feeds

I would simply create a network resource on the server hosting the feed, with write access to a specific AD development group.

Thus, your repository is publicly available, and only some people can add packages to it.

Even after you have a continuous integration server, you can only allow account creation packages to access the file share (or API key). Thus, packages are published automatically after passing automatic tests.