20 Nov, 2013

4 commits


19 Nov, 2013

3 commits


13 Nov, 2013

1 commit


11 Nov, 2013

1 commit


07 Nov, 2013

1 commit


05 Nov, 2013

1 commit


03 Nov, 2013

1 commit

  • The blocked? method is used to check whether a user exists in LDAP. Prior to this change, if the LDAP server had more objects below the one pointed to by the DN, those objects would also be picked up by the search, causing the method to determine the user should be blocked.
    
    One case where this can happen is when using Active Directory and a user have a mobile phone assigned. In this case, Exchange will add an entry called ExchangeActiveSyncDevices under the users entry. The user-visible behaviour is then that a user loses Gitlab access when he enables a mobile device.
    
    This fix sets the search scope to BaseObject in order to ensure that only the user itself is returned.
    Elias Mårtenson
     

01 Nov, 2013

2 commits


31 Oct, 2013

1 commit


29 Oct, 2013

1 commit


24 Oct, 2013

2 commits


15 Oct, 2013

1 commit


07 Oct, 2013

1 commit


04 Oct, 2013

2 commits


22 Sep, 2013

2 commits


14 Sep, 2013

1 commit


11 Sep, 2013

2 commits


04 Sep, 2013

5 commits


03 Sep, 2013

1 commit


02 Sep, 2013

3 commits


27 Aug, 2013

1 commit


26 Aug, 2013

2 commits


25 Aug, 2013

1 commit

  • Any mention of Issues, MergeRequests, or Commits via GitLab-flavored markdown
    references in descriptions, titles, or attached Notes creates a back-reference
    Note that links to the original referencer. Furthermore, pushing commits with
    commit messages that match a (configurable) regexp to a project's default
    branch will close any issues mentioned by GFM in the matched closing phrase.
    If accepting a merge request would close any Issues in this way, a banner is
    appended to the merge request's main panel to indicate this.
    ash wilson