Subversion Authentication

Choose your Authentication Method

Sublime supports two authentication methods: Subversion Authentication, and LDAP Authentication with Active Directory. When using Subversion authentication you create and manage user accounts directly within Sublime. In addition, users can change their own passwords directly from the web interface.

With LDAP Authentication users authenticate using their existing Active Directory username and password. Sublime allows administrators to provide an LDAP query to target exactly which users in the organization should have access. For more information, see our installation guide.

Manage Users

Administrators can create and manage Subversion user accounts from the Sublime web interface. Once users are created and assigned a password they can log into Sublime and access Subversion repositories. Users can manage their own email address and password from the Sublime web interface reducing the burden on your administrators. When your server is configured for LDAP authentication, user accounts are picked up automatically as they are added or removed from Active Directory.

Create User Groups

To simplify permission management, Sublime allows you to create user groups or use Active Directory security groups. When granting access to a repository, adding a group grants all users in that group access to the repository. In addition, groups can be nested within each other allowing you to create a flexible permission hierarchy. Clicking on the name of a group in Sublime pops up a window showing all members of that group. This makes it extremely easy to see who will be granted access when creating new repositories or managing repository permissions.

Manage Repository Permissions

Managing repository permissions is simple and intuitive in Sublime. When creating a new repository, users can select users and groups to grant access. Repository owners can manage the permissions of their own repositories without having to involve server administrators. This helps ensure that users always have the correct access to their repositories when they need it.