BigW Consortium Gitlab

  1. 31 Aug, 2017 1 commit
    • `current_application_settings` belongs on `Gitlab::CurrentSettings` · 5883ce95
      Sean McGivern authored
      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.
  2. 06 Apr, 2017 1 commit
  3. 31 Mar, 2017 1 commit
  4. 21 Dec, 2016 1 commit
  5. 11 Nov, 2016 1 commit
    • Centralize LDAP config/filter logic · c50b98da
      Drew Blessing authored
      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.
  6. 03 Aug, 2016 2 commits
  7. 06 Jun, 2016 1 commit
    • Add a `U2fRegistrations` table/model. · 791cc913
      Timothy Andrew authored
      - 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.
  8. 03 Jun, 2016 2 commits
  9. 12 May, 2016 3 commits
  10. 24 Feb, 2016 1 commit
    • Move "I should see Crowd login form" feature to a view spec · b95ef77e
      Robert Speicher authored
      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.
  11. 06 Jan, 2016 1 commit
  12. 24 Dec, 2015 1 commit
  13. 03 Nov, 2015 1 commit
  14. 24 Sep, 2015 1 commit
    • Remove 'kerberos' from auth_helper.rb for gitlab-CE. · 7d2655aa
      Ben Rosser authored
      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
  15. 16 Sep, 2015 1 commit
  16. 09 Sep, 2015 1 commit
  17. 02 Sep, 2015 1 commit
  18. 26 Aug, 2015 1 commit
  19. 23 Jul, 2015 1 commit