-
- Downloads
Don't allow blocked users to authenticate through other means
Gitlab::Auth.find_with_user_password is currently used in these places: - resource_owner_from_credentials in config/initializers/doorkeeper.rb, which is used for the OAuth Resource Owner Password Credentials flow - the /session API call in lib/api/session.rb, which is used to reveal the user's current authentication_token In both cases users should only be authenticated if they're in the active state.
Showing
- lib/gitlab/auth.rb 1 addition, 1 deletionlib/gitlab/auth.rb
- spec/lib/gitlab/auth_spec.rb 12 additions, 0 deletionsspec/lib/gitlab/auth_spec.rb
- spec/requests/api/doorkeeper_access_spec.rb 18 additions, 0 deletionsspec/requests/api/doorkeeper_access_spec.rb
- spec/requests/api/oauth_tokens_spec.rb 22 additions, 0 deletionsspec/requests/api/oauth_tokens_spec.rb
- spec/requests/api/session_spec.rb 18 additions, 0 deletionsspec/requests/api/session_spec.rb
- spec/requests/git_http_spec.rb 10 additions, 2 deletionsspec/requests/git_http_spec.rb
Please register or sign in to comment