summaryrefslogtreecommitdiff
path: root/app/helpers/auth_helper.rb
Commit message (Collapse)AuthorAgeFilesLines
* Exclude LDAP from OmniauthCallbackController base methodsJames Edwards-Jones2018-04-301-2/+6
|
* Moved o_auth/saml/ldap modules under gitlab/authHoratiu Eugen Vlad2018-02-281-3/+3
|
* use Gitlab::UserSettings directly as a singleton instead of ↵Mario de la Ossa2018-02-021-3/+1
| | | | including/extending it
* `current_application_settings` belongs on `Gitlab::CurrentSettings`Sean McGivern2017-08-311-0/+2
| | | | | | | | | | | | | | | | The initializers including this were doing so at the top level, so every object loaded after them had a `current_application_settings` method. However, if someone had rack-attack enabled (which was loaded before these initializers), it would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't have that method. To fix this: 1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need `Object.new.current_application_settings` to work. 2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it like that in several places. 3. Change the initializers to use that new form.
* Move AuthHelper#two_factor_skippable? into ApplicationControllerMarkus Koller2017-04-061-12/+0
|
* Prevent users from disconnecting gitlab account from CASTiago Botelho2017-03-311-0/+4
|
* Added support for Authentiq oauth providerAlex2016-12-211-1/+1
|
* Centralize LDAP config/filter logicDrew Blessing2016-11-111-1/+1
| | | | | | | | | Centralize all LDAP config logic in `GitLab::LDAP::Config`. Previously, some logic was in the Devise initializer and it was not honoring the `user_filter`. If a user outside the configured `user_filter` signed in, an account would be created but they would then be denied access. Now that logic is centralized, the filter is honored and users outside the filter are never created.
* Add a `U2fRegistrations` table/model.Timothy Andrew2016-06-061-1/+1
| | | | | | | | | | | | | | - To hold registrations from U2F devices, and to authenticate them. - Previously, `User#two_factor_enabled` was aliased to the `otp_required_for_login` column on `users`. - This commit changes things a bit: - `User#two_factor_enabled` is not a method anymore - `User#two_factor_enabled?` checks both the `otp_required_for_login` column, as well as `U2fRegistration`s - Change all instances of `User#two_factor_enabled` to `User#two_factor_enabled?` - Add the `u2f` gem, and implement registration/authentication at the model level.
* enabled_button_based_providers.any? instead of ! empty? for ↵Andrei Gliga2016-05-121-1/+1
| | | | button_based_providers_enabled?
* method to check if oauth button based providers are enabledAndrei Gliga2016-05-121-0/+4
|
* method to get the enabled_button_based_providersAndrei Gliga2016-05-121-0/+6
|
* Move "I should see Crowd login form" feature to a view specrs-crowd-form-view-specRobert Speicher2016-02-241-0/+4
| | | | | | | | We were doing all kinds of code gymnastics to "enable" Crowd in the feature spec and this would sometimes cause a transient failure. Really what it's testing is if the Crowd login form shows when Crowd's enabled, so this is much better suited to a view spec.
* Enable Microsoft Azure OAuth2 supportJanis Meybohm2016-01-061-1/+1
|
* Grace period support for TFAGabriel Mazetto2015-12-241-0/+12
|
* Add Facebook authenticationDouwe Maan2015-11-031-1/+1
|
* Remove 'kerberos' from auth_helper.rb for gitlab-CE.Ben Rosser2015-09-241-1/+1
| | | | | | | There is no Kerberos auth in gitlab-ce, so it shouldn't be noted as a form-driven auth mechanism in app/helpers/auth_helper.rb. This breaks using Kerberos as a custom omniauth provider. See issue #2510
* Eliminate combined image_tag and image_path in providers listStan Hu2015-09-161-1/+1
|
* Crowd integrationValery Sizov2015-09-021-1/+5
|
* Allow custom label to be set for authentication providers.auth-icons-labelsDouwe Maan2015-07-231-0/+50
View Lorry Controller Status