Introduction to authentication modes
Compare the authentication modes that Unity Version Control On-Prem supports, and choose the mode that fits your environment.
読み終わるまでの所要時間 2 分最終更新 15時間前
Unity Version Control (UVCS) On-Prem supports several authentication modes. Each mode uses a different source for its list of users and a different way to identify users. Choose a mode based on the operating systems in your environment and the identity provider that your organization uses.
How UVCS identifies users
A UVCS client sends security information to the server for validation. The basic token that the client sends is the security identifier (SEID). Each authentication mode builds the SEID in a different way and gets its list of users from a different source.
Choose an authentication mode
The following table compares the available authentication modes:
Mode | User source | SEID contents | When to use the mode |
|---|---|---|---|
| Local name | Local users on the server machine | User name | Your network is secure, and clients and server share user names. |
| Name and ID | Local users on the server machine | User name and ID | All machines run the same operating system family, and share user names and IDs. |
| LDAP | LDAP server | ID from the LDAP mechanism | Your organization uses an LDAP server, including in mixed Windows and Unix environments. |
| Active Directory | Active Directory main server | Windows security identifier (SID) | Your server runs on Windows and your organization uses Active Directory. |
| User and password | | User name and encoded password | You don't use LDAP or Active Directory, or your machines have no common user login. |
| SAML | Microsoft Entra ID | Internal UVCS token | Your organization uses Microsoft Entra ID for single sign-on. |
To change the mode that your server uses, refer to Change authentication mode.