title: Private intranet-level Nuget feed: Windows Integrated Security customization
body: <p>I'm considering setting up Intranet-level Nuget feed(bunch of teams in my company are supposed to use it).<br>
  I've looked briefly through some tutorials + appropriate chapters in <a href="https://rads.stackoverflow.com/amzn/click/com/1430241918" rel="nofollow noreferrer" rel="nofollow noreferrer">Pro Nuget</a> book, however I still do have some question left so far:  </p>
  
  <ol>
  <li>How to make windows integrated security working on private feed smoothly and customize access rights for private Nuget feed(for instance, grant everyone to get packages but grant pushing only to several domain users/groups); </li>
  <li>How to allow developers to push packages to private feed without having <code>api key</code>?</li>
  <li>How to save developers from making such silly mistake as pushing package to public feed? Is that enough to not configure <code>api key</code> for public feed as default?</li>
  </ol>
  
  <p>Has anyone faced with one of these cases?</p>