- 06 Nov, 2017 1 commit
-
-
Douwe Maan authored
-
- 05 Oct, 2017 1 commit
-
-
Tiago Botelho authored
-
- 02 Oct, 2017 1 commit
-
-
Tiago Botelho authored
-
- 28 Sep, 2017 2 commits
-
-
James Lopez authored
-
James Lopez authored
-
- 25 Sep, 2017 1 commit
-
-
Tiago Botelho authored
-
- 06 Sep, 2017 1 commit
-
-
Alexander Keramidas authored
-
- 02 Aug, 2017 1 commit
-
-
Robin Bobbitt authored
-
- 12 Jul, 2017 1 commit
-
-
Nick Thomas authored
-
- 23 Jun, 2017 2 commits
-
-
James Lopez authored
-
James Lopez authored
-
- 07 Jun, 2017 1 commit
-
-
Robin Bobbitt authored
-
- 25 Apr, 2017 1 commit
-
-
Douwe Maan authored
-
- 13 Apr, 2017 1 commit
-
-
geoandri authored
-
- 27 Mar, 2017 1 commit
-
-
George Andrinopoulos authored
-
- 01 Mar, 2017 1 commit
-
-
Sean McGivern authored
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 30 Nov, 2016 1 commit
-
-
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.
-
- 10 Nov, 2016 1 commit
-
-
Drew Blessing authored
-
- 29 Jun, 2016 1 commit
-
-
Patricio Cano authored
Fixed privilege escalation issue where manually set external users would be reverted back to internal users if they logged in via OAuth and that provider was not in the `external_providers` list.
-
- 22 Jun, 2016 1 commit
-
-
Drew Blessing authored
-
- 08 Jun, 2016 1 commit
-
-
Patricio Cano authored
-
- 07 Jun, 2016 1 commit
-
-
Patricio Cano authored
-
- 06 Jun, 2016 1 commit
-
-
Patricio Cano authored
-
- 11 Apr, 2016 2 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
-
- 18 Feb, 2016 4 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
-
Douwe Maan authored
This reverts commit c04e22fb, reversing changes made to 0feab326.
-
Patricio Cano authored
-
- 19 Jan, 2016 1 commit
-
-
Douwe Maan authored
-
- 15 Jan, 2016 1 commit
-
-
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.
-
- 22 Dec, 2015 1 commit
-
-
Patricio Cano authored
-
- 17 Jun, 2015 1 commit
-
-
Alex Lossent authored
Code tweaks in 45e9150a caused the ldap_person method to not return expected results. Improved tests to cover the ldap_person method, which was previously stubbed.
-
- 05 Jun, 2015 1 commit
-
-
Douwe Maan authored
-
- 03 Jun, 2015 1 commit
-
-
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.
-
- 13 May, 2015 1 commit
-
-
Douwe Maan authored
-
- 09 Apr, 2015 1 commit
-
-
Robert Speicher authored
Lets Rails autoload these files by name
-
- 27 Mar, 2015 1 commit
-
-
Douwe Maan authored
-