An error occurred fetching the project authors.
  1. 15 Sep, 2015 1 commit
  2. 02 Sep, 2015 1 commit
  3. 19 Aug, 2015 1 commit
  4. 18 Aug, 2015 1 commit
  5. 24 Jul, 2015 2 commits
  6. 23 Jul, 2015 1 commit
  7. 06 Jul, 2015 1 commit
  8. 13 Jun, 2015 1 commit
  9. 11 Jun, 2015 1 commit
  10. 09 Jun, 2015 2 commits
  11. 03 Jun, 2015 1 commit
    • Alex Lossent's avatar
      Add option to automatically link omniauth and LDAP identities · dfcea8ed
      Alex Lossent authored
      Until now, a user needed to first sign in with his LDAP identity and then manually
      link his/her account with an omniauth identity from their profile.
      Only when this is done can the user authenticate with the omniauth provider and at
      the same time benefit from the LDAP integration (HTTPS authentication with LDAP
      username/password and in EE: LDAP groups, SSH keys etc.).
      This feature automates the process by looking up a corresponding LDAP person when a
      user connects with omniauth for the first time and then automatically linking the LDAP
      and omniauth identities (of course, like the existing allow_single_sign_on setting,
      this is meant to be used with trusted omniauth providers).
      The result is identical to a manual account link.
      
      Add config initializers for other omniauth settings.
      dfcea8ed
  12. 29 May, 2015 1 commit
  13. 27 May, 2015 1 commit
  14. 16 May, 2015 1 commit
  15. 06 May, 2015 2 commits
  16. 03 May, 2015 1 commit
  17. 02 May, 2015 1 commit
  18. 26 Apr, 2015 1 commit
  19. 14 Apr, 2015 2 commits
  20. 13 Apr, 2015 1 commit
  21. 03 Apr, 2015 1 commit
  22. 30 Mar, 2015 2 commits
  23. 27 Mar, 2015 2 commits
  24. 24 Mar, 2015 1 commit
  25. 11 Mar, 2015 1 commit
  26. 07 Mar, 2015 1 commit
  27. 24 Feb, 2015 1 commit
  28. 10 Feb, 2015 1 commit
  29. 07 Feb, 2015 1 commit
  30. 28 Jan, 2015 1 commit
  31. 22 Jan, 2015 1 commit
  32. 20 Jan, 2015 1 commit
  33. 19 Jan, 2015 1 commit
  34. 06 Jan, 2015 1 commit
    • Jacob Vosmaer's avatar
      White-list requests from 127.0.0.1 · af56c1dd
      Jacob Vosmaer authored
      On some misconfigured GitLab servers, if you look in production.log it looks
      like all requests come from 127.0.0.1. To avoid unwanted banning we
      white-list 127.0.0.1 with this commit.
      af56c1dd