30 Jun, 2014
2 commits
-
Conflicts: CHANGELOG Gemfile Gemfile.lock VERSION app/views/projects/edit.html.haml config.ru config/gitlab.yml.example lib/gitlab/backend/grack_auth.rb lib/gitlab/upgrader.rb
13 Jun, 2014
1 commit
04 Sep, 2013
1 commit
02 Sep, 2013
1 commit
20 Dec, 2012
1 commit
12 Sep, 2012
1 commit
31 Aug, 2012
2 commits
24 Aug, 2012
2 commits
21 Aug, 2012
1 commit
-
Conflicts: app/models/user.rb
17 Aug, 2012
1 commit
29 Jul, 2012
1 commit
21 Jul, 2012
1 commit
-
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 f322975. This resolves issue #1077. Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
16 Jul, 2012
1 commit
-
Gitlab requires an email address for all user accounts as this is the default account id and is used for sending notifications. LDAP accounts may be missing email fields so handle this by showing a sensible error message before redirecting to the login screen again. Resolves github issue #899 Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>
17 Feb, 2012
1 commit
-
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.
28 Jan, 2012
1 commit
