An error occurred fetching the project authors.
  1. 08 Sep, 2015 1 commit
  2. 29 Aug, 2015 1 commit
  3. 21 Aug, 2015 1 commit
  4. 14 Apr, 2015 2 commits
  5. 13 Apr, 2015 1 commit
  6. 09 Apr, 2015 1 commit
  7. 06 Apr, 2015 1 commit
  8. 29 Jan, 2015 1 commit
  9. 04 Dec, 2014 2 commits
  10. 14 Oct, 2014 2 commits
  11. 13 Oct, 2014 1 commit
  12. 10 Oct, 2014 1 commit
  13. 08 Sep, 2014 2 commits
  14. 04 Sep, 2014 1 commit
  15. 03 Sep, 2014 2 commits
  16. 01 Sep, 2014 1 commit
  17. 29 Aug, 2014 1 commit
    • Jacob Vosmaer's avatar
      Remove LDAP::Access#find_user · 614ca3ec
      Jacob Vosmaer authored
      This method existed to allow LDAP users to take over existing GitLab
      accounts if the part before the '@' of their LDAP email attribute
      matched the username of an existing GitLab user. I propose to disable
      this behavior in order to prevent unintended GitLab account takeovers.
      
      After this change it is still possible to take over an existing GitLab
      account with your LDAP credentials, as long as the GitLab account email
      address matches the LDAP user email address.
      614ca3ec
  18. 11 Jun, 2014 1 commit
  19. 28 Mar, 2014 1 commit
    • Jacob Vosmaer's avatar
      Use omniauth nickname as the username for LDAP · 2e6b5370
      Jacob Vosmaer authored
      Before there was a bug in omniauth-ldap which prevented samaccountname
      showing up as a possible username for new LDAP users. Thanks to upstream
      fixes, we no longer need to work around this bug.
      2e6b5370
  20. 10 Mar, 2014 1 commit
  21. 18 Feb, 2014 1 commit
  22. 19 Jan, 2014 1 commit
  23. 01 Dec, 2013 1 commit
  24. 03 Nov, 2013 1 commit
    • Elias Mårtenson's avatar
      When looking up a user by DN, use single scope · bc8a875d
      Elias Mårtenson authored
      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.
      bc8a875d
  25. 07 Oct, 2013 1 commit
  26. 23 Sep, 2013 2 commits
    • Izaak Alpert's avatar
      Update for readability · 8a8123a3
      Izaak Alpert authored
      fixed a test a broke in the configurable theme PR
      Change-Id: Id894506941bc01ab0d259d48ca7ff9b80bb2c57e
      8a8123a3
    • Izaak Alpert's avatar
      Allows username only updates to ldap properties · 4fcc17e6
      Izaak Alpert authored
      -when logging in if users are allowed to login with just usernames in ldap we will update uid of the user if their uid is out of date
      
      Conflicts:
      	spec/lib/auth_spec.rb
      
      Change-Id: Ia171b3d5133da86edc18c0d08ecfaf6a174f2574
      4fcc17e6
  27. 03 Sep, 2013 1 commit
  28. 02 Sep, 2013 2 commits