Technical differences compared to vanilla Gerrit

Version 16.7 of the TeamForge–Git integration is based on a slightly modified version of Gerrit 2.13.x. Here's how this version is different from vanilla Gerrit.

Possible ways of authentication:
- TeamForge account / password (for ssh and http Git operations, Gerrit Web interface)
- TeamForge SSO (Gerrit Web interface)
- TeamForge account / public key is stored in TeamForge Authorized Key settings (ssh Git operations)
- TeamForge account / Gerrit http password (http Git operations)
- Basic Auth using TeamForge account / password for Gerrit REST/RPC API (Digest is not supported)
User data (email addresses, full names, ssh keys) is managed from TeamForge account settings
A Gerrit project is created by creating a Git repository in TeamForge
Gerrit ACLs are based on TeamForge project role memberships
Gerrit ACLs are determined based on TeamForge SCM access permissions for the project role in question
TeamForge project roles of logged-in users show up in Gerrit > Settings > Groups but do not show up in Gerrit > People > List Groups (only internal groups show up here)
Gerrit project names must follow TeamForge repository conventions (Unix conventions, no spaces, / or capital letters)
Additional features: History Protection, TeamForge code review policies, TeamForge commit object creation, TeamForge artifact associations, TeamForge SOAP API to script repository, user and RBAC operations, enhanced branding support.