1. 03 Oct, 2015 1 commit
  2. 23 Jul, 2015 1 commit
  3. 06 Jul, 2015 1 commit
  4. 05 Jun, 2015 1 commit
  5. 27 May, 2015 1 commit
  6. 13 May, 2015 1 commit
  7. 08 Feb, 2015 1 commit
  8. 12 Jan, 2015 1 commit
  9. 10 Jan, 2015 1 commit
  10. 04 Dec, 2014 2 commits
  11. 17 Oct, 2014 1 commit
  12. 16 Oct, 2014 2 commits
  13. 14 Oct, 2014 1 commit
  14. 13 Oct, 2014 1 commit
  15. 10 Oct, 2014 1 commit
  16. 06 Aug, 2014 1 commit
  17. 24 Jun, 2014 2 commits
  18. 13 Jun, 2014 1 commit
  19. 03 Sep, 2013 1 commit
  20. 02 Sep, 2013 1 commit
  21. 20 Dec, 2012 1 commit
  22. 12 Sep, 2012 1 commit
  23. 02 Sep, 2012 1 commit
  24. 31 Aug, 2012 2 commits
  25. 24 Aug, 2012 1 commit
  26. 17 Aug, 2012 1 commit
  27. 29 Jul, 2012 1 commit
  28. 21 Jul, 2012 1 commit
    • Pat Thoyts's avatar
      Handle LDAP missing credentials error with a flash message. · 8d12048d05f3
      Pat Thoyts authored
      If a user fails to provide a username or password to the LDAP login
      form then a 500 error is returned due to an exception being raised
      in omniauth-ldap. This gem has been amended to use the omniauth
      error propagation function (fail!) to pass this exception message to
      the registered omniauth failure handler so that the Rails application
      can handle it approriately.
      
      The failure function now knows about standard exceptions and no longer
      requires a specific check for the OmniAuth::Error exception added by
      commit 8a5f3e252474
      
      .
      
      This resolves issue #1077.
      Signed-off-by: default avatarPat Thoyts <patthoyts@users.sourceforge.net>
      8d12048d05f3
  29. 16 Jul, 2012 1 commit
  30. 17 Feb, 2012 1 commit
    • Steve Prentice's avatar
      Use the omniauth-ldap info object instead of the raw ldap info in extra. · 6e3c18bf4294
      Steve Prentice authored
      This helps with compatibility with more LDAP providers as the implementation
      doesn't depend on the exact names of the LDAP fields. The LDAP strategy
      helps maps the attributes to the fields in the info object and we use the
      info object to get the email and name.
      
      This makes the LDAP auth compatible with most OpenLDAP servers as well.
      6e3c18bf4294
  31. 28 Jan, 2012 1 commit