title: What are the best practices for creating a Nexus private repository group for proxy repositories requiring authentication
body: <p>One of the Maven repositories I want to proxy through my Nexus repository is private, <em>i.e.</em>, it requires a username/password for access. So, I set up a proxy repository the usual way and entered my credentials under the authentication settings. So far, so good. </p>
  
  <p>Now, normally I would add the new repository to the public repository group. But, as I understand it, this will allow anyone with access to my repository to access this private repository through mine, without authentication. Is this correct?</p>
  
  <p>Can I solve this issue by creating a private repository group containing the new repository? I would then have to make a new repository target privilege in order to restrict access to the new private group, right? </p>
  
  <p>I think the next step would be to create a new <code>&lt;profile&gt;</code> and <code>&lt;repository&gt;</code> in my <code>settings.xml</code>, as well as a corresponding <code>&lt;mirror&gt;</code>. And, finally, I'll need to exclude the new repository URL pattern from my default <code>&lt;mirror&gt;</code> (<em>e.g.</em>, <code>&lt;mirrorOf&gt;*,!thirdparty,!private&lt;/mirror&gt;</code>).</p>
  
  <p>Am I on the right track? Making this harder than it needs to be? Or missing something? </p>