| | |
| | | # SINCE 0.5.0
|
| | | realm.minPasswordLength = 5
|
| | |
|
| | | # URL of the LDAP server.
|
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.server = ldap://localhost
|
| | |
|
| | | # Login username for LDAP searches.
|
| | | # The domain prefix may be omitted if it matches the domain specified in
|
| | | # *realm.ldap.domain*. If this value is unspecified, anonymous LDAP login will
|
| | | # be used.
|
| | | # |
| | | # e.g. mydomain\\username
|
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.username = cn=Directory Manager
|
| | |
|
| | | # Login password for LDAP searches.
|
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.password = password
|
| | |
|
| | | # The LdapUserService must be backed by another user service for standard user
|
| | | # and team management.
|
| | | # default: users.conf
|
| | | #
|
| | | # SINCE 1.0.0
|
| | | # RESTART REQUIRED
|
| | | realm.ldap.backingUserService = users.conf
|
| | |
|
| | | # Delegate team membership control to LDAP.
|
| | | #
|
| | | # If true, team user memberships will be specified by LDAP groups. This will
|
| | | # disable team selection in Edit User and user selection in Edit Team.
|
| | | #
|
| | | # If false, LDAP will only be used for authentication and Gitblit will maintain
|
| | | # team memberships with the *realm.ldap.backingUserService*.
|
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.maintainTeams = false
|
| | |
|
| | | # Root node that all Users sit under in LDAP
|
| | | #
|
| | | # This is the root node that searches for user information will begin from in LDAP
|
| | | # If blank, it will search ALL of ldap. |
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.accountBase = OU=Users,OU=UserControl,OU=MyOrganization,DC=MyDomain
|
| | |
|
| | | # Filter Criteria for Users in LDAP
|
| | | #
|
| | | # Query pattern to use when searching for a user account. This may be any valid |
| | | # LDAP query expression, including the standard (&) and (|) operators. Variables may
|
| | | # be injected via the ${variableName} syntax. Recognized variables are:
|
| | | # ${username} - The text entered as the user name
|
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.accountPattern = (&(objectClass=person)(sAMAccountName=${username}))
|
| | |
|
| | | # Root node that all Teams sit under in LDAP
|
| | | #
|
| | | # This is the node that searches for team information will begin from in LDAP
|
| | | # If blank, it will search ALL of ldap. |
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.groupBase = OU=Groups,OU=UserControl,OU=MyOrganization,DC=MyDomain
|
| | |
|
| | | # Filter Criteria for Teams in LDAP
|
| | | #
|
| | | # Query pattern to use when searching for a team. This may be any valid |
| | | # LDAP query expression, including the standard (&) and (|) operators. Variables may
|
| | | # be injected via the ${variableName} syntax. Recognized variables are:
|
| | | # ${username} - The text entered as the user name
|
| | | # ${dn} - The Distinguished Name of the user logged in
|
| | | # All attributes on the User's record are also passed in. For example, if a user has an
|
| | | # attribute "fullName" set to "John", "(fn=${fullName})" will be translated to "(fn=John)".
|
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.groupMemberPattern = (&(objectClass=group)(member=${dn}))
|
| | |
|
| | | # Users and or teams that are Admins, read from LDAP
|
| | | #
|
| | | # This is a space delimited list. If it starts with @, it indicates a Team Name |
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.admins= @Git_Admins
|
| | |
|
| | | # Attribute(s) on the USER record that indicate their display (or full) name. Leave blank
|
| | | # for no mapping available in LDAP
|
| | | #
|
| | | # This may be a single attribute, or a string of multiple attributes. Examples:
|
| | | # displayName - Uses the attribute 'displayName' on the user record
|
| | | # ${personalTitle}. ${givenName} ${surname} - Will concatenate the 3 |
| | | # attributes together, with a '.' after personalTitle |
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.displayName= displayName
|
| | |
|
| | | # Attribute(s) on the USER record that indicate their email address. Leave blank
|
| | | # for no mapping available in LDAP
|
| | | #
|
| | | # This may be a single attribute, or a string of multiple attributes. Examples:
|
| | | # email - Uses the attribute 'email' on the user record
|
| | | # ${givenName}.${surname}@gitblit.com -Will concatenate the 2 attributes
|
| | | # together with a '.' and '@' creating something like first.last@gitblit.com |
| | | #
|
| | | # SINCE 1.0.0
|
| | | realm.ldap.email = email
|
| | |
|
| | | #
|
| | | # Gitblit Web Settings
|
| | | #
|
| | |
| | | # SINCE 0.5.0
|
| | | web.allowZipDownloads = true
|
| | |
|
| | | # Allow optional Lucene integration. Lucene indexing is an opt-in feature.
|
| | | # A repository may specify branches to index with Lucene instead of using Git
|
| | | # commit traversal. There are scenarios where you may want to completely disable
|
| | | # Lucene indexing despite a repository specifying indexed branches. One such
|
| | | # scenario is on a resource-constrained federated Gitblit mirror.
|
| | | #
|
| | | # SINCE 0.9.0
|
| | | web.allowLuceneIndexing = true
|
| | |
|
| | | # Use Clippy (Flash solution) to provide a copy-to-clipboard button.
|
| | | # If false, a button with a more primitive JavaScript-based prompt box will
|
| | | # offer a 3-step (click, ctrl+c, enter) copy-to-clipboard alternative.
|