summaryrefslogtreecommitdiffstats
path: root/src/test/java/com/gitblit/tests/LdapAuthenticationTest.java
Commit message (Collapse)AuthorAgeFilesLines
* Create base unit test class for LDAP tests.Florian Zschocke2016-11-231-332/+7
| | | | | | 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.
* Set "can admin" permission on LDAP users and teams correctlymerged--fixAdminRoleLDAPFlorian Zschocke2016-11-181-4/+261
| | | | | | | | | | | | | | | | | | | | | | | 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.
* Extend LDAP tests to use LDAP servers with access restrictions.Florian Zschocke2016-11-091-45/+257
| | | | | | | | | | | | | | Add access restrictions to the LDAP test server instances. New modes used a test parameters are ANONYMOUS, DS_MANAGER and USR_MANAGER. ANONYMOUS can bind anonymously and access users and groups. In DS_MANAGER the server requires authentication and will only allow the DIRECTORY_MANAGER user to search for users and groups. In USR_MANAGER only the user can search groups, the USER_MANAGER, which is used to bind in this mode, can not. A third server instance is created because I did fear side effects should the tests be run in parallel, had I tried to configure the access restriction in Before.
* Extend LDAP authentication tests to use different modes.Florian Zschocke2016-11-061-23/+107
| | | | | | | Instantiate two LDAP servers, one that allows anonymous access, and one that requires authentication for all operations. The JUnit test is parameterized to run all tests with both instances. It uses different settings for each mode.
* Log update for Fail2Ban usagePaul Martin2015-10-251-6/+6
| | | | | + Adds standard logging for all authentication providers + Updates help page to use default GitBlit SSH port
* Create infrastructure for XSS sanitizationJames Moger2014-09-071-2/+6
|
* Add repository and user/team lifecycle listener extension pointsJames Moger2014-06-091-5/+5
|
* LDAP: Added test for binding without special account (e.g. userbasedJani Averbach2014-03-311-0/+13
| | | bind)
* Fix authentication security hole with external providersJames Moger2014-03-181-0/+36
|
* Fixed and introduced tests for synching ldap users and groups.Alfred Schmid2014-02-211-22/+19
| | | | | | | | Using new settings key realm.ldap.synchronize Switched from key String to Keys class. To avoid letting tests pass with hardcoded keys wich doesn't exist anymore. Now on Key Refactorings the test gets compile error again. Test the isReady behavior from LdapSyncService.
* API adjustments and elimination of duplicate config optionsJames Moger2014-02-191-5/+5
|
* Load empty groups as empty teams from ldap, when ldap userAlfred Schmid2014-02-191-0/+28
| | | | synchronization is enabled.
* Fixed Tests, use local copy of users.conf. Initialize reset ldap beforeAlfred Schmid2014-02-191-12/+31
| | | | every test.
* Basic implementation of feature for ldap user synchronization asAlfred Schmid2014-02-191-3/+40
| | | | | background service. Introduced configuration property to configure the synchronization period.
* Refactor user services and separate authentication (issue-281)James Moger2013-11-291-0/+165
Change-Id: I336e005e02623fc5e11a4f8b4408bea5465a43fd
generated by cgit v1.2.3 (git 2.39.1) at 2025-05-12 13:14:18 +0000