BigW Consortium Gitlab

  1. 06 Nov, 2017 1 commit
  2. 05 Oct, 2017 1 commit
  3. 02 Oct, 2017 1 commit
  4. 28 Sep, 2017 2 commits
  5. 25 Sep, 2017 1 commit
  6. 06 Sep, 2017 1 commit
  7. 02 Aug, 2017 1 commit
  8. 12 Jul, 2017 1 commit
  9. 23 Jun, 2017 2 commits
  10. 07 Jun, 2017 1 commit
  11. 25 Apr, 2017 1 commit
  12. 13 Apr, 2017 1 commit
  13. 27 Mar, 2017 1 commit
  14. 01 Mar, 2017 1 commit
  15. 23 Feb, 2017 2 commits
  16. 30 Nov, 2016 1 commit
    • Improve the `Gitlab::OAuth::User` error message · 374033fe
      Drew Blessing authored
      The error saving the user is logged to application.log. Previously,
      the entry had no context and was unusable - 'Error saving user:
      [Email address already taken]'. Adding the auth hash UID and email
      makes the error more helpful.
  17. 10 Nov, 2016 1 commit
  18. 29 Jun, 2016 1 commit
  19. 22 Jun, 2016 1 commit
  20. 08 Jun, 2016 1 commit
  21. 07 Jun, 2016 1 commit
  22. 06 Jun, 2016 1 commit
  23. 11 Apr, 2016 2 commits
  24. 18 Feb, 2016 4 commits
  25. 19 Jan, 2016 1 commit
  26. 15 Jan, 2016 1 commit
    • Fix signup for some OAuth providers · 2444c040
      Steffen Köhler authored
      some OAuth providers (kerberos for example) only provide a username and an email, but no name. Therefore
      a signup fails because the name is empty. Best guess for the name is
      probably the username, therefore use it as name.
  27. 22 Dec, 2015 1 commit
  28. 17 Jun, 2015 1 commit
  29. 05 Jun, 2015 1 commit
  30. 03 Jun, 2015 1 commit
    • 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.
  31. 13 May, 2015 1 commit
  32. 09 Apr, 2015 1 commit
  33. 27 Mar, 2015 1 commit