gitlab-org--gitlab-foss/config/initializers/warden.rb

58 lines
1.7 KiB
Ruby
Raw Normal View History

Rails.application.configure do |config|
Warden::Manager.after_set_user(scope: :user) do |user, auth, opts|
Gitlab::Auth::UniqueIpsLimiter.limit_user!(user)
activity = Gitlab::Auth::Activity.new(opts)
case opts[:event]
when :authentication
activity.user_authenticated!
when :set_user
activity.user_authenticated!
activity.user_session_override!
when :fetch # rubocop:disable Lint/EmptyWhen
# We ignore session fetch events
else
activity.user_session_override!
2018-07-20 10:00:28 -04:00
end
end
2018-05-02 04:08:16 -04:00
Warden::Manager.after_authentication(scope: :user) do |user, auth, opts|
2018-05-02 04:08:16 -04:00
ActiveSession.cleanup(user)
end
Warden::Manager.after_set_user(scope: :user, only: :fetch) do |user, auth, opts|
2018-05-02 04:08:16 -04:00
ActiveSession.set(user, auth.request)
end
Warden::Manager.before_failure(scope: :user) do |env, opts|
Gitlab::Auth::Activity.new(opts).user_authentication_failed!
2018-05-02 04:08:16 -04:00
end
Warden::Manager.before_logout(scope: :user) do |user, auth, opts|
user ||= auth.user
activity = Gitlab::Auth::Activity.new(opts)
tracker = Gitlab::Auth::BlockedUserTracker.new(user, auth)
ActiveSession.destroy(user, auth.request.session.id)
activity.user_session_destroyed!
##
# It is possible that `before_logout` event is going to be triggered
# multiple times during the request lifecycle. We want to increment
# metrics and write logs only once in that case.
#
# 'warden.auth.*' is our custom hash key that follows usual convention
# of naming keys in the Rack env hash.
#
next if auth.env['warden.auth.user.blocked']
if user.blocked?
activity.user_blocked!
tracker.log_activity!
end
auth.env['warden.auth.user.blocked'] = true
2018-05-02 04:08:16 -04:00
end
end