# Either the full path to a user config file (users.conf)\r
# OR the full path to a simple user properties file (users.properties)\r
# OR a fully qualified class name that implements the IUserService interface.\r
-# Any custom implementation must have a public default constructor.\r
+#\r
+# Alternative user services:\r
+# com.gitblit.LdapUserService\r
+#\r
+# Any custom user service implementation must have a public default constructor.\r
#\r
# SINCE 0.5.0\r
# RESTART REQUIRED\r
realm.ldap.server = ldap://localhost\r
\r
# Login username for LDAP searches.\r
-# The domain prefix may be omitted if it matches the domain specified in\r
-# *realm.ldap.domain*. If this value is unspecified, anonymous LDAP login will\r
-# be used.\r
+# If this value is unspecified, anonymous LDAP login will be used.\r
# \r
# e.g. mydomain\\username\r
#\r
# SINCE 1.0.0\r
realm.ldap.maintainTeams = false\r
\r
-# Root node that all Users sit under in LDAP\r
+# Root node for all LDAP users\r
#\r
-# This is the root node that searches for user information will begin from in LDAP\r
-# If blank, it will search ALL of ldap. \r
+# This is the root node from which subtree user searches will begin.\r
+# If blank, Gitblit will search ALL nodes.\r
#\r
# SINCE 1.0.0\r
realm.ldap.accountBase = OU=Users,OU=UserControl,OU=MyOrganization,DC=MyDomain\r
\r
-# Filter Criteria for Users in LDAP\r
+# Filter criteria for LDAP users\r
#\r
# Query pattern to use when searching for a user account. This may be any valid \r
-# LDAP query expression, including the standard (&) and (|) operators. Variables may\r
-# be injected via the ${variableName} syntax. Recognized variables are:\r
+# LDAP query expression, including the standard (&) and (|) operators.\r
+#\r
+# Variables may be injected via the ${variableName} syntax.\r
+# Recognized variables are:\r
# ${username} - The text entered as the user name\r
#\r
# SINCE 1.0.0\r
realm.ldap.accountPattern = (&(objectClass=person)(sAMAccountName=${username}))\r
\r
-# Root node that all Teams sit under in LDAP\r
+# Root node for all LDAP groups to be used as Gitblit Teams\r
#\r
-# This is the node that searches for team information will begin from in LDAP\r
-# If blank, it will search ALL of ldap. \r
+# This is the root node from which subtree team searches will begin.\r
+# If blank, Gitblit will search ALL nodes. \r
#\r
# SINCE 1.0.0\r
realm.ldap.groupBase = OU=Groups,OU=UserControl,OU=MyOrganization,DC=MyDomain\r
\r
-# Filter Criteria for Teams in LDAP\r
+# Filter criteria for LDAP groups\r
#\r
# Query pattern to use when searching for a team. This may be any valid \r
-# LDAP query expression, including the standard (&) and (|) operators. Variables may\r
-# be injected via the ${variableName} syntax. Recognized variables are:\r
+# LDAP query expression, including the standard (&) and (|) operators.\r
+#\r
+# Variables may be injected via the ${variableName} syntax.\r
+# Recognized variables are:\r
# ${username} - The text entered as the user name\r
# ${dn} - The Distinguished Name of the user logged in\r
-# All attributes on the User's record are also passed in. For example, if a user has an\r
-# attribute "fullName" set to "John", "(fn=${fullName})" will be translated to "(fn=John)".\r
+#\r
+# All attributes from the LDAP User record are available. For example, if a user\r
+# has an attribute "fullName" set to "John", "(fn=${fullName})" will be \r
+# translated to "(fn=John)".\r
#\r
# SINCE 1.0.0\r
realm.ldap.groupMemberPattern = (&(objectClass=group)(member=${dn}))\r
\r
-# Users and or teams that are Admins, read from LDAP\r
+# LDAP users or groups that should be given administrator privileges.\r
+#\r
+# Teams are specified with a leading '@' character. Groups with spaces in the\r
+# name can be entered as "@team name".\r
#\r
-# This is a space delimited list. If it starts with @, it indicates a Team Name \r
+# e.g. realm.ldap.admins = john @git_admins "@git admins"\r
#\r
+# SPACE-DELIMITED\r
# SINCE 1.0.0\r
realm.ldap.admins= @Git_Admins\r
\r
### Integration with Your Infrastructure\r
\r
- Groovy push hook scripts\r
-- Pluggable user service mechanism for custom authentication, authorization, and user management\r
+- Pluggable user service mechanism\r
+ - LDAP authentication with optional LDAP-controlled Team memberships\r
+ - Custom authentication, authorization, and user management\r
- Rich RSS feeds\r
- JSON-based RPC mechanism\r
- [Java Client RSS/JSON API library](http://code.google.com/p/gitblit/downloads/detail?name=%API%) for custom integration\r
\r
[jgit]: http://eclipse.org/jgit "Eclipse JGit Site"\r
[git]: http://git-scm.com "Official Git Site"\r
-[rhcloud]: https://openshift.redhat.com/app "RedHat OpenShift"
\ No newline at end of file
+[rhcloud]: https://openshift.redhat.com/app "RedHat OpenShift"\r
- Administrators may create, edit, rename, or delete teams through the web UI or RPC interface\r
- Repository Owners may edit repositories through the web UI\r
- Administrators and Repository Owners may set the default branch through the web UI or RPC interface\r
+- LDAP authentication and optional LDAP-controlled Team memberships\r
- Gravatar integration\r
- Git-notes display support\r
- gh-pages display support (Jekyll is not supported)\r
### Caveats\r
- Gitblit may have security holes. Patches welcome. :)\r
\r
-[jgit]: http://eclipse.org/jgit "Eclipse JGit Site"
\ No newline at end of file
+[jgit]: http://eclipse.org/jgit "Eclipse JGit Site"\r
#### User Roles\r
There are two actual *roles* in Gitblit: *#admin*, which grants administrative powers to that user, and *#notfederated*, which prevents an account from being pulled by another Gitblit instance. Administrators automatically have access to all repositories. All other *roles* are repository names. If a repository is access-restricted, the user must have the repository's name within his/her roles to bypass the access restriction. This is how users are granted access to a restricted repository.\r
\r
-## Authentication and Authorization Customization\r
+## Alternative Authentication and Authorization\r
\r
-### Customize Authentication Only\r
+### LDAP Authentication\r
+*SINCE 1.0.0*\r
+\r
+LDAP can be used to authenticate Users and optionally control Team memberships. When properly configured, Gitblit will delegate authentication to your LDAP server and will cache some user information in the usual users file (.conf or .properties).\r
+\r
+When using the LDAP User Service, new user accounts can not be manually created from Gitblit. Gitblit user accounts are automatically created for new users on their first succesful authentication through Gitblit against the LDAP server. It is also important to note that the LDAP User Service does not retrieve or store user passwords nor does it implement any LDAP-write functionality.\r
+\r
+To use the *LdapUserService* set *realm.userService=com.gitblit.LdapUserService* in your `gitblit.properties` file or your `web.xml` file and then configure the *realm.ldap* settings appropriately for your LDAP environment.\r
+\r
+#### Example LDAP Layout\r
+\r
+\r
+Please see [ldapUserServiceSampleData.ldif](https://github.com/gitblit/gitblit/blob/master/tests/com/gitblit/tests/resources/ldapUserServiceSampleData.ldif) to see the data in LDAP that reflects the above picture.\r
+\r
+#### Gitblit Settings for Example LDAP Layout\r
+The following are the settings required to configure Gitblit to authenticate against the example LDAP server with LDAP-controlled team memberships.\r
+\r
+<table class="table">\r
+<thead>\r
+<tr><th>parameter</th><th>value</th><th>description</th></tr>\r
+</thead>\r
+<tbody>\r
+<tr>\r
+ <th>realm.ldap.server</th><td>ldap://localhost:389</td>\r
+ <td>Tells Gitblit to connect to the LDAP server on localhost port 389. The URL Must be of form ldap(s)://<server>:<port> with port being optional (389 for ldap, 636 for ldaps).</td>\r
+</tr>\r
+<tr>\r
+ <th>realm.ldap.username</th><td>cn=Directory Manager</td>\r
+ <td>The credentials that will log into the LDAP server</td>\r
+</tr>\r
+<tr>\r
+ <th>realm.ldap.password</th><td>password</td>\r
+ <td>The credentials that will log into the LDAP server</td>\r
+</tr>\r
+<tr>\r
+ <th>realm.ldap.backingUserService</th><td>users.conf</td>\r
+ <td>Where to store all information that is used by Gitblit. All information will be synced here upon user login.</td>\r
+</tr>\r
+<tr>\r
+ <th>realm.ldap.maintainTeams</th><td>true</td>\r
+ <td>Are team memberships maintained in LDAP (<em>true</em>) or manually in Gitblit (<em>false</em>).</td>\r
+</tr>\r
+<tr>\r
+ <th>realm.ldap.accountBase</th><td>OU=Users,OU=UserControl,OU=MyOrganization,DC=MyDomain</td>\r
+ <td>What is the root node for all users in this LDAP system. Subtree searches will start from this node.</td>\r
+</tr>\r
+<tr>\r
+ <th>realm.ldap.accountPattern</th><td>(&(objectClass=person)(sAMAccountName=${username}))</td><td>The LDAP search filter that will match a particular user in LDAP. ${username} will be replaced with whatever the user enters as their username in the Gitblit login panel.</td>\r
+</tr>\r
+<tr>\r
+ <th>realm.ldap.groupBase</th><td>OU=Groups,OU=UserControl,OU=MyOrganization,DC=MyDomain</td>\r
+ <td>What is the root node for all teams in this LDAP system. Subtree searches will start from this node.</td>\r
+</tr>\r
+<tr>\r
+ <th>realm.ldap.groupMemberPattern</th><td>(&(objectClass=group)(member=${dn}))</td><td>The LDAP search filter that will match all teams for the authenticating user. ${username} will be replaced with whatever the user enters as their username in the Gitblit login panel. Anything else in ${} will be replaced by Attributes from the User node.</td>\r
+</tr>\r
+<tr>\r
+ <th>realm.ldap.admins</th><td>@Git_Admins</td><td>A space-delimited list of usernames and/or teams that indicate admin status in Gitblit. Teams are referenced with a leading <em>@</em> character.</td>\r
+</tr>\r
+</tbody>\r
+</table>\r
+\r
+#### LDAP In-Memory Server\r
+\r
+You can start Gitblit GO with an in-memory LDAP server by specifying the *--ldapLdifFile* command-line argument. The LDAP server will listen on localhost of the port specified in *realm.ldap.url* of `gitblit.properties`. Additionally, a root user record is automatically created for *realm.ldap.username* and *realm.ldap.password*. Please note that the ldaps:// protocol is not supported for the in-memory server.\r
+\r
+### Custom Authentication\r
This is the simplest choice where you implement custom authentication and delegate all other standard user and team operations to one of Gitblit's user service implementations. This choice insulates your customization from changes in User and Team model classes and additional API that may be added to IUserService.\r
\r
Please subclass [com.gitblit.GitblitUserService](https://github.com/gitblit/gitblit/blob/master/src/com/gitblit/GitblitUserService.java) and override the *setup()* and *authenticate()* methods. \r
\r
Your subclass must be on Gitblit's classpath and must have a public default constructor. \r
\r
-### Customize Everything\r
+### Custom Everything\r
Instead of maintaining a `users.conf` or `users.properties` file, you may want to integrate Gitblit into an existing environment.\r
\r
You may use your own custom *com.gitblit.IUserService* implementation by specifying its fully qualified classname in the *realm.userService* setting.\r
My testing indicates that your username must be embedded in the url. YMMV. \r
<pre>https://username@yourserver/git/your/repository</pre>\r
\r
-## LDAP Support\r
-*SINCE 1.0.0*\r
-\r
-LDAP can be used with Gitblit to read Users and the Teams that they belong to. If configured, LDAP will be queried upon every login to the system, and synchronize that information with the traditional Gitblit backed file (.conf or .properties). This "lazy" reading approach provides for fast reaction times, but will force a user to log in before you can maintain them (or their teams).\r
-\r
-### Example Diagram (with attributes)\r
-\r
-\r
-Please see <gitblit>/tests/com/gitblit/tests/resources/ldapUserServiceSampleData.ldif to see the data in LDAP that reflects the above picture.\r
-\r
-### GitBlit Properties (See gitblit.properties for full description)\r
-The following is are descriptions of the properties that would follow the sample layout of an LDAP (or Active Directory) setup above.\r
-\r
-<table border="1" cellpadding="1" cellspacing="1">\r
-<tr>\r
- <td>realm.ldap.server</td><td>ldap://localhost:389</td>\r
- <td>Tells Gitblit to connect to the LDAP server on localhost, port 389. URL Must be of form ldap(s)://<server>:<port> with port being optional (389 for ldap, 636 for ldaps).</td>\r
-</tr>\r
-<tr>\r
- <td>realm.ldap.username</td><td>cn=Directory Manager</td>\r
- <td>The credentials that will log into this gitblit server</td>\r
-</tr>\r
-<tr>\r
- <td>realm.ldap.password</td><td>password</td>\r
- <td>The credentials that will log into this gitblit server</td>\r
-</tr>\r
-<tr>\r
- <td>realm.ldap.backingUserService</td><td>users.conf</td>\r
- <td>Where to store all information that is used by Gitblit. All information will be synced here upon user login.</td>\r
-</tr>\r
-<tr>\r
- <td>realm.ldap.maintainTeams</td><td>true</td>\r
- <td>Are users maintained in LDAP (true), or manually in Gitblit (false).</td>\r
-</tr>\r
-<tr>\r
- <td>realm.ldap.accountBase</td><td>OU=Users,OU=UserControl,OU=MyOrganization,DC=MyDomain</td>\r
- <td>What is the root node for all users in this LDAP system. Searches will be subtree searches starting from this node.</td>\r
-</tr>\r
-<tr>\r
- <td>realm.ldap.accountPattern</td><td>(&(objectClass=person)(sAMAccountName=${username}))</td><td>The LDAP Search filter that will match a particular user in LDAP. ${username} will be replaced with whatever the user types in as their user name.</td>\r
-</tr>\r
-<tr>\r
- <td>realm.ldap.groupBase</td><td>OU=Groups,OU=UserControl,OU=MyOrganization,DC=MyDomain</td>\r
- <td>What is the root node for all teams in this LDAP system. Searches will be subtree searches starting from this node.</td>\r
-</tr>\r
-<tr>\r
- <td>realm.ldap.groupMemberPattern</td><td>(&(objectClass=group)(member=${dn}))</td><td>The LDAP Search filter that will match all teams for the logging in user in LDAP. ${username} will be replaced with whatever the user types in as their user name. Anything else in ${} will be replaced by Attributes on the User node.</td>\r
-</tr>\r
-<tr>\r
- <td>realm.ldap.admins</td><td>@Git_Admins</td><td>A space delimited list of users and teams (if starting with @) that indicate admin status in Gitblit.</td>\r
-</tr>\r
-</table>\r
-\r
-You may notice that there are no properties to find the password on the User record. This is intentional, and the service utilizes the LDAP login process to verify that the user credentials are correct.\r
-\r
-You can also start Gitblit GO with an in-memory (backed by an LDIF file) LDAP server by using the --ldapLdifFile property. It will listen where ever gitblit.settings is pointed to. However, it only supports ldap...not ldaps, so be sure to set that in gitblit.settings. It reads the user / password in gitblit.settings to create the root user login.\r
-\r
-Finally, writing back to LDAP is not implemented at this time, so do not worry about corrupting your corporate LDAP. Many orgnizations are likely to go through a different flow to update their LDAP, so it's unlikely that this will become a feature.
\ No newline at end of file
\r
**%VERSION%** ([go](http://code.google.com/p/gitblit/downloads/detail?name=%GO%) | [war](http://code.google.com/p/gitblit/downloads/detail?name=%WAR%) | [express](http://code.google.com/p/gitblit/downloads/detail?name=%EXPRESS%) | [fedclient](http://code.google.com/p/gitblit/downloads/detail?name=%FEDCLIENT%) | [manager](http://code.google.com/p/gitblit/downloads/detail?name=%MANAGER%) | [api](http://code.google.com/p/gitblit/downloads/detail?name=%API%)) based on [%JGIT%][jgit] *released %BUILDDATE%*\r
\r
+#### changes\r
+\r
+- IUserService interface has changed to better accomodate custom authentication and/or custom authorization\r
+\r
+#### additions\r
+\r
+- Added LDAP User Service with many new *realm.ldap* keys (Github/jcrygier)\r
+\r
+**0.9.3** *released 2012-04-11*\r
+\r
#### fixes\r
\r
- Fixed bug where you could not remove all selections from a RepositoryModel list (permitted users, permitted teams, hook scripts, federation sets, etc) (issue 81)\r
\r
private TeamModel createTeamFromLdap(SearchResultEntry teamEntry) {\r
TeamModel answer = new TeamModel(teamEntry.getAttributeValue("cn"));\r
- // If attributes other than team name ever from from LDAP, this is where to get them\r
+ // potentially retrieve other attributes here in the future\r
\r
return answer; \r
}\r
\r
private UserModel createUserFromLdap(String simpleUserName, SearchResultEntry userEntry) {\r
UserModel answer = new UserModel(simpleUserName);\r
- //If attributes other than user name ever from from LDAP, this is where to get them\r
+ // potentially retrieve other attributes here in the future\r
\r
return answer;\r
}\r
projects / gitblit.git / commitdiff