title: Is it possible to setup Gerrit for GIT without using per person SSH certificates
body: <p>I am trying to setup GIT + GERRIT infrastructure for my team. We are part of bigger company. Company with procedures and practices.</p>
  
  <p>Upto now we have been using SVN, which allows for LDAP authentication. We basically were able to commit using username and password.</p>
  
  <p>Now I have been struggling for several days with the GIT configuration. I know that theoretically speaking it is possible to configure GIT to use such pairs of username/password for the commits instead of SSH certificates.</p>
  
  <p>However, I am pretty decided on code reviews and GERRIT. Now as I started reading it seems that <strong>there is no way to configure account in GERRIT if you do not configure SSH key for it</strong>. This seems to me like double authentication as we already expose Gerrit through https and have credentials for controlling the access. Also I do not think I have the influence to make the admins either:</p>
  
  <ul>
  <li>provide per account SSH keys through the LDAP</li>
  <li>configure the keys for each instance of Gerrit (as we have many repositories we want to migrate)</li>
  </ul>
  
  <p>Currently if I do not find a way around that maybe my quest for migration to GIT will fail. Is there a way to configure GIT to work with gerrit without providing per person SSH certificate? I still need to be able to distinguish as commiters all the users in significant LDAP directory.</p>