- Feb 21, 2012
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Conflicts: app/views/layouts/_project_menu.html.haml
-
vsizov authored
-
- Feb 20, 2012
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
vsizov authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- Feb 19, 2012
-
-
Valery Sizov authored
-
Valery Sizov authored
-
Valery Sizov authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Valery Sizov authored
-
Valery Sizov authored
-
Valery Sizov authored
-
Valery Sizov authored
-
Valery Sizov authored
-
Valery Sizov authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Valeriy Sizov authored
This makes gitlabhq compatible with more LDAP servers (specifically OpenLDAP).
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
-
Dmitriy Zaporozhets authored
Fixes :public Warning In Resque When Running Any Rails Command
-
- Feb 18, 2012
-
-
Ryan Lovelett authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- Feb 17, 2012
-
-
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.
-
- Feb 16, 2012
-
-
Dmitriy Zaporozhets authored
-