summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Add DocValues to support sorting of ticket index fields.Florian Zschocke2017-03-051-0/+7
| | | | | | | | | | | | | In order to support sorting, Lucene 5 needs DocValue fields in an index. So in order to make the ticket index work, i.e. show any tickets on the tickets page, the ticket index needs to be changed, adding a DocValues field. The DocValuesFields are implemented for the current index, which does not use multiple values for a field. Should at any time in the future an existing numeric field get multiple values stored in a document, then the index needs to know that and use SortedNumeric DocValues and SortFields instead.
* Replace deprecated BooleanQuery constructor with builder.Florian Zschocke2017-03-052-15/+13
| | | | | Also replace deprecated `search` method with the one without a filter argument, since the filter isn't used anyhow.
* Update link target to Lucene 5.5 query syntax, moving the link to the page.Florian Zschocke2017-03-0516-119/+139
| | | | | | | | | | | | | | | Update the link target to the query parser syntax page of the 5.5 version. Refactor the `LuceneSearchPage` to use an `ExternalLink` for the link to the lucene page, so that the link target is kept and updated in the Java code. Move the link out of the language files. This was way too cumbersome to update the link target (which is probably why no one ever did). The query help text is changed to contain a variable: `gb.queryHelp = here be some ${querySyntax} help`, which is replaced by Wicket with a link. The link text is a new lange file property: `gb.querySyntax`.
* Remove obsolete Lucene version constants.Florian Zschocke2017-03-052-6/+0
|
* Bump to Lucene 5.5.2Luca Milanesio2017-03-052-26/+26
|
* Better Czech localizationJan Breuer2017-03-031-76/+76
|
* Prevent last column on Tree page from wrapingJan Breuer2017-02-201-0/+1
| | | | | With localizations, there can be longer text then 13em so there is a line break. This fix prevent this line breaking and thus every line has normal height again.
* Fix #1114 HttpUtils getGitblitURL does not support nonstandard portsJan Breuer2017-02-151-1/+3
| | | | | X-Forwarded-Host can contain port number and it is added twice in that situation This fix just prevent adding port number if it is already there
* Add Czech localeJan Breuer2017-02-155-0/+854
|
* Merge pull request #1192 from mystygage/listBranchForRepositoryJames Moger2017-02-082-1/+6
|\ | | | | List branches from only one repository if a repository name is given
| * List branches from only one repository if a repository name is givenMarkus Fömpe2017-01-262-1/+6
| | | | | | | | | | | | e.g.: https://localhost:8443/rpc/?req=LIST_REPOSITORY_BRANCHES&name=repo.git Fix #1184
* | New Setting "Default Language" when creating user.william2017-02-084-29/+71
| |
* | fix bug "get user default language null exception"william2017-01-251-1/+5
| |
* | Sending email (certificate zip file) based on locale that user selectedwilliam2017-01-246-5/+160
|/
* when apache terminates https, the Ajax-Location header needs to be rewritten ↵RainerW2017-01-231-0/+1
| | | | as well
* Merge pull request #6 from fzs/sshAuthMethodsFlorian Zschocke2017-01-212-9/+52
|\ | | | | Set list of offered SSH authentication methods.
| * Set list of offered SSH authentication methods.merged--sshAuthMethodsFlorian Zschocke2016-12-062-9/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make the SSH authentication methods used by the server configurable, so that for example password authentication can be turned off. For this, a `git.sshAuthenticationMethods` setting is added which is a space separated list of authentication method names. Only the methods listed will be enabled in the server. This is modeled after the option of the same name from sshd_config, but it does not offer listing multiple required methods. It leaves the door open, though, for a later extension to support such a multi-factor authentication. Since this also includes Kerberos authentication with GSS API, this obsoletes the `git.sshWithKrb5` property. The latter is removed. Instead, to enable Kerberos5 authentication, add the method name `gssapi-with-mic` to the authentication methods list.
* | Update weblogic.xmlBala Raman2017-01-161-2/+2
| | | | | | Update to web app 3.0 xsd
* | Update to web.xml, fix to #1132Bala Raman2017-01-151-4/+4
| | | | | | | | | | Update to web.xml, fix to #1132 Fixes to namespace to fix xml parse error, where strict validation required
* | Merge pull request #1171 from pingunaut/usermanager-file-instantiationJames Moger2017-01-062-2/+25
|\ \ | | | | | | Update UserManager to support construction of IUserServices with IRuntimeManager as a constructor parameter
| * | extracted methodMartin Spielmann2017-01-061-9/+20
| | |
| * | updated commentde4c9d2016-12-301-1/+1
| | |
| * | update user manager to support instantiation if IUserService with ↵de4c9d2016-12-302-2/+14
| | | | | | | | | | | | IRuntimeManager as a parameter
* | | Update korean translation for gitblit new version.DONGSU, KIM2017-01-051-718/+759
|/ /
* | Fix typo in defaults.properties.Florian Zschocke2016-12-181-1/+1
| |
* | Merge pull request #1160 from fzs/sshLdapAuthenticatorFlorian Zschocke2016-12-1814-625/+2276
|\ \ | | | | | | LDAP SSH key manager
| * | Extend documentation in default.properties and LdapKeyManager.java.merged--sshLdapAuthenticatorFlorian Zschocke2016-12-062-2/+31
| | |
| * | The public key manager can disable writing keys, which hides commandsFlorian Zschocke2016-12-066-12/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some public key mangers may be read-only, i.e. not allow to add or delete keys, or to change the key comment or assigned permissions. In such a case the respective commands should not be available on the SSH shell and the SSH Keys panel should also not offer the possibility. The `IPublicKeyManager` gets three new methods, modelled after the `AuthenticationManager`: `supportsWritingKeys`, `supportsCommentChanges` and `supportsPermissionChanges`. They return true if a key manager allows for keys to be written or updated. For example the existing `FileKeyManager` will return true for all three since it allows to store and update keys in a file. The new `LdapKeyManager` returns false since it only accesses LDAP and can not add or update any keys in the directory. A future key manager might get keys from an LDAP directory but still keep comments and permissions for it in a local copy. If writing of keys is not supported: * the welcome shell does not suggest adding a key, * the `SshKeysDispatcher` does not offer the "add", "remove", "comment" and "permission" commands, and * the SSH keys panel hides the "delete" button in the key list, and the "Add Key" form. The hiding of the "Add key" form is not perfect since the surrounding div is still shown, but I don't know how to hide it and it didn't look too bad, either.
| * | Fix SshKeysDispatcher test failing on WindowsFlorian Zschocke2016-12-061-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | The `SshKeysDispatcher` tests that use the keys list command are failing on Windows because they assume a Unix line ending after each key. But the command will use a system line ending. So this fix uses system line endings in the reference string for the assert, too. In addition, two `assertTrue(false)´ are replaced with a proper `fail`.
| * | Use dynamic port selection for LDAP listeners in LDAP tests.Florian Zschocke2016-12-061-10/+11
| | | | | | | | | | | | | | | | | | | | | Instead of using fixed ports for the listeners of the in-memory LDAP server, let the listeners select ports and then save them in the authentication mode instance. This way we prevent port collisions, which especially showed up under Windows.
| * | Retrieve public SSH keys from LDAP.Florian Zschocke2016-11-296-37/+1248
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add new class `LdapPublicKeyManager` which retrieves public SSH keys from LDAP. The attribute can be configured with the new configuration option `realm.ldap.sshPublicKey`. The setting can be a simple attribute name, like `sshPublicKey`, or an attribute name and a prefix for the value, like `altSecurityIdentities:SshKey`, in which case attributes are selected that have the name `altSecurityIdentities` and whose values start with `SshKey:`.
| * | Extract LdapConnection into new class from LdapAuthProviderFlorian Zschocke2016-11-233-268/+543
| | | | | | | | | | | | | | | | | | | | | | | | Extract the inner class `LdapConnection` from the `LdapAuthProvider` into a separate class, so that it can be used from multiple classes that have to connect to an LDAP directory. The new class is placed into the new package `com.gitblit.ldap`, since it isn't specific to authentication.
| * | Create base unit test class for LDAP tests.Florian Zschocke2016-11-232-332/+416
| | | | | | | | | | | | | | | | | | Extract the creation of the in-memory servers and the interceptor code to a base class that LDAP related unit tests can extend to have the servers available.
* | | Remove duplicate import of class SecureRandomFlorian Zschocke2016-12-151-1/+0
| | | | | | | | | | | | | | | Fixes the build that was broken by cherry-picking commit 2be2c2, which resulted in an import collision on the `SecureRandom` class.
* | | Merge pull request #1167 from fzs/secureCookiesJames Moger2016-12-142-1/+16
|\ \ \ | | | | | | | | Secure cookies
| * | | Set secure session cookies when redirecting from HTTP to HTTPS.merged--secureCookiesFlorian Zschocke2016-12-101-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | So far for session cookies the secure property was only set when no HTTP port was opened. This changes to also set it when HTTP is redirected to the HTTPS port.
| * | | Set secure user cookies and only for HTTP.Florian Zschocke2016-12-101-0/+14
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | Mark the user authentication cookie to be only used for HTTP, making it inaccessible for JavaScript engines. If only HTTPS is used and no HTTP (i.e. also if HTTP is redirected to HTTPS) then mark the user cookie to be sent only over secure connections.
* | | Merge branch 'rcaa-master' into master.Florian Zschocke2016-12-1313-12/+136
|\ \ \
| * | | Introduce SecureRandom wrapper for properly seeded static instancesFlorian Zschocke2016-12-123-5/+121
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce our own wrapper `SecureRandom` around `java.security.SecureRandom`. This a) makes sure that the PRNG is seeded on creation and not when random bytes are retrieved, and b) uses a static instance in the `UserModel` so that lags do not occur during operation due to potentially seeding getting blocked on Unix when reading from the system's entropy pool. To keep the random data still secure, the static instance will reseed all 24 hours, also a functionality of the wrapper class. This fixes #1063 and extends and closes PR #1116
| * | | changing Math.random to SecureRandomrcaa2016-12-111-1/+5
| | | |
| * | | removing unecessary user cookie codeRodrigo Andrade2016-08-157-8/+8
| | | |
| * | | removing duplicated code for cookie genaration and adding random bytes to ↵Rodrigo Andrade2016-08-155-4/+8
| | | | | | | | | | | | | | | | generate user cookies
* | | | Merge branch 'fixMentionsInTickets-985'Florian Zschocke2016-12-125-7/+88
|\ \ \ \
| * | | | Fix user mention regular expression and group replacement.merged--fixMentionsInTickets-985Florian Zschocke2016-12-105-5/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The regular expression used for user mentions used to work only inside sentences. Also, since it tested for whitespace, the whitespace would get replaced, too, which would join lines together. Instead the new regex uses boundary matchers to match against word boundaires. As these are not capturing only the actual user mention can be captured and is then replaced. Also, this way the regex can ignore punctuation like in "@jim, look at this." Since Gibtlit now requires Java 7 we can use named capture groups. This makes the use of a centrally defined regular expression much safer. The (admittedly only) group to capture the user name is named "user" and can be referenced by this name. By using the name instead of a group number, the regex could be changed without the code using it breaking because the group number changed. A simple test is added for user mentions, which unfortunately has to deal with the full markdown replacement, too. Fixes #985
| * | | | Use REGEX_TICKET_MENTION instead of hardcoded regular expressionGlenn Matthys2016-12-103-3/+6
| | | | |
| * | | | Introduce new constant REGEX_TICKET_MENTIONGlenn Matthys2016-12-101-0/+6
| | |/ / | |/| |
* | | | Merge pull request #1152 from fzs/fixAdminRoleLDAPJames Moger2016-11-183-19/+296
|\ \ \ \ | | |_|/ | |/| | Set "can admin" permission on LDAP users and teams correctly
| * | | Set "can admin" permission on LDAP users and teams correctlymerged--fixAdminRoleLDAPFlorian Zschocke2016-11-183-19/+296
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The canAdmin permission is set on a LDAP user, when the user is listed in `realm.ldap.admins` or is a member of a team listed in `realm.ldap.admins`. This leads to inconsistent and surprising behaviour on the EditUser page when clicking the "can admin" checkbox. Also, the "can admin" checkbox is disabled, but not checked, for teams that are listed as admin teams. The new behaviour implemented in this patch makes users and teams from LDAP match local ones. That means: * LDAP teams that are listed in `realm.ldap.admins` get the canAdmin property set if teams are maintained in LDAP. * LDAP users that are listed in `realm.ldap.admins` get the canAdmin property set if teams are maintained in LDAP. * LDAP users do not get the canAdmin property set, if they are only a member of a team listed in `realm.ldap.admins`. * The `supportsRoleChanges` method for users and teams of the `LdapAuthProvider` unconditially returns false if teams are maintained in LDAP, not only for users and teams listed in `realm.ldap.admins`. * Therefore, for all LDAP users and teams the "can admin" checkbox is always disabled if teams are maintained in LDAP.
* | | | Merge pull request #1147 from tomaswolf/disabled_pager_linksJames Moger2016-11-143-2/+29
|\ \ \ \ | | | | | | | | | | Fix disabled links in PagerPanel
| * | | | Fix disabled links in PagerPanelTom2016-10-313-2/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Disabled links in the PagerPanel (used on the LuceneSearchPage to page through search results) were only rendered as "disabled". The links themselves remained active, which gives strange effects when clicked. For instance it was possible to move to result pages -1, -2, and so on. Really disable the links. Add missing CSS rules to have correct styling as Wicket renders disabled links as spans, not anchors. Include the new CSS file in BasePage.html. And add the left/right arrows only if not on the first/last page.
generated by cgit v1.2.3 (git 2.39.1) at 2025-05-13 12:02:17 +0000