title: Repository Group authentication on settings.xml
body: <p>I'm generating a maven settings.xml for this scenario with nexus:</p>
  
  <ul>
  <li>my-releases-repo </li>
  <li>my-snapshots-repo</li>
  </ul>
  
  <p>both into my-group and I have a role which allows the user to crud on my-group.</p>
  
  <p>So, in settings.xml is defined the server, with id as my-group and it's corresponding user and passwd. Of course is defined too the repository into an a active profile, as this:</p>
  
  <pre><code>&lt;repositories&gt;
     &lt;repository&gt;
        &lt;id&gt;my-group&lt;/id&gt;
        &lt;releases&gt;
           &lt;enabled&gt;true&lt;/enabled&gt;
           &lt;checksumPolicy&gt;warn&lt;/checksumPolicy&gt;
        &lt;/releases&gt;
        &lt;snapshots&gt;
           &lt;enabled&gt;true&lt;/enabled&gt;
           &lt;updatePolicy&gt;always&lt;/updatePolicy&gt;
           &lt;checksumPolicy&gt;warn&lt;/checksumPolicy&gt;
        &lt;/snapshots&gt;
        &lt;url&gt;http://my.nexus.corp/content/groups/my-group&lt;/url&gt;
     &lt;/repository&gt;
  </code></pre>
  
  <p>With this configuration the user is able to authenticate to both repositories and download artifact from them, but not to deploy.</p>
  
  <p>Finally the question is: the server authentication provided in settings.xml applies only for read,view methods when it's defined for a repository group? </p>
  
  <p>Of course, if I add servers pointing to each repository-id (without adding these repositories on profile, only keeping my-group) the deploy works.</p>
  
  <p>My idea is to provide a simplier settings.xml using repository group authentication, avoiding to set the password for each server (repo) because it's the same user.</p>