2016-11-15 15:56:29 +00:00
|
|
|
# frozen_string_literal: true
|
|
|
|
|
2016-03-05 21:43:05 +00:00
|
|
|
class Auth::SessionsController < Devise::SessionsController
|
2024-01-19 12:19:49 +00:00
|
|
|
include Redisable
|
|
|
|
|
|
|
|
MAX_2FA_ATTEMPTS_PER_HOUR = 10
|
|
|
|
|
2016-03-05 21:43:05 +00:00
|
|
|
layout 'auth'
|
2016-03-27 23:06:52 +01:00
|
|
|
|
2023-10-23 16:46:21 +01:00
|
|
|
skip_before_action :check_self_destruct!
|
2017-01-28 19:43:38 +00:00
|
|
|
skip_before_action :require_no_authentication, only: [:create]
|
Change unconfirmed user login behaviour (#11375)
Allow access to account settings, 2FA, authorized applications, and
account deletions to unconfirmed and pending users, as well as
users who had their accounts disabled. Suspended users cannot update
their e-mail or password or delete their account.
Display account status on account settings page, for example, when
an account is frozen, limited, unconfirmed or pending review.
After sign up, login users straight away and show a simple page that
tells them the status of their account with links to account settings
and logout, to reduce onboarding friction and allow users to correct
wrongly typed e-mail addresses.
Move the final sign-up step of SSO integrations to be the same
as above to reduce code duplication.
2019-07-22 09:48:50 +01:00
|
|
|
skip_before_action :require_functional!
|
2020-11-12 22:05:01 +00:00
|
|
|
skip_before_action :update_user_sign_in
|
Change unconfirmed user login behaviour (#11375)
Allow access to account settings, 2FA, authorized applications, and
account deletions to unconfirmed and pending users, as well as
users who had their accounts disabled. Suspended users cannot update
their e-mail or password or delete their account.
Display account status on account settings page, for example, when
an account is frozen, limited, unconfirmed or pending review.
After sign up, login users straight away and show a simple page that
tells them the status of their account with links to account settings
and logout, to reduce onboarding friction and allow users to correct
wrongly typed e-mail addresses.
Move the final sign-up step of SSO integrations to be the same
as above to reduce code duplication.
2019-07-22 09:48:50 +01:00
|
|
|
|
2022-06-21 14:16:22 +01:00
|
|
|
prepend_before_action :check_suspicious!, only: [:create]
|
|
|
|
|
2023-11-30 14:39:41 +00:00
|
|
|
include Auth::TwoFactorAuthenticationConcern
|
2019-09-24 03:35:36 +01:00
|
|
|
|
2022-11-17 21:59:07 +00:00
|
|
|
content_security_policy only: :new do |p|
|
|
|
|
p.form_action(false)
|
|
|
|
end
|
|
|
|
|
2016-03-27 23:06:52 +01:00
|
|
|
def create
|
2019-09-24 03:35:36 +01:00
|
|
|
super do |resource|
|
2021-06-21 16:07:30 +01:00
|
|
|
# We only need to call this if this hasn't already been
|
|
|
|
# called from one of the two-factor or sign-in token
|
|
|
|
# authentication methods
|
|
|
|
|
|
|
|
on_authentication_success(resource, :password) unless @on_authentication_success_called
|
2016-03-27 23:06:52 +01:00
|
|
|
end
|
|
|
|
end
|
2016-09-26 22:55:21 +01:00
|
|
|
|
2017-01-28 19:43:38 +00:00
|
|
|
def destroy
|
2018-09-09 03:10:44 +01:00
|
|
|
tmp_stored_location = stored_location_for(:user)
|
2017-01-28 19:43:38 +00:00
|
|
|
super
|
2019-09-18 15:37:27 +01:00
|
|
|
session.delete(:challenge_passed_at)
|
2017-05-27 12:04:28 +01:00
|
|
|
flash.delete(:notice)
|
2018-09-09 03:10:44 +01:00
|
|
|
store_location_for(:user, tmp_stored_location) if continue_after?
|
2017-01-28 19:43:38 +00:00
|
|
|
end
|
|
|
|
|
Add WebAuthn as an alternative 2FA method (#14466)
* feat: add possibility of adding WebAuthn security keys to use as 2FA
This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor
to the Settings page for editing the 2FA methods – now it will list the
methods that are available to the user (TOTP and WebAuthn) and from
there they'll be able to add or remove any of them.
Also, it's worth mentioning that for enabling WebAuthn it's required to
have TOTP enabled, so the first time that you go to the 2FA Settings
page, you'll be asked to set it up.
This work was inspired by the one donde by Github in their platform, and
despite it could be approached in different ways, we decided to go with
this one given that we feel that this gives a great UX.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: add request for WebAuthn as second factor at login if enabled
This commits adds the feature for using WebAuthn as a second factor for
login when enabled.
If users have WebAuthn enabled, now a page requesting for the use of a
WebAuthn credential for log in will appear, although a link redirecting
to the old page for logging in using a two-factor code will also be
present.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: add possibility of deleting WebAuthn Credentials
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: disable WebAuthn when an Admin disables 2FA for a user
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: remove ability to disable TOTP leaving only WebAuthn as 2FA
Following examples form other platforms like Github, we decided to make
Webauthn 2FA secondary to 2FA with TOTP, so that we removed the
possibility of removing TOTP authentication only, leaving users with
just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA'
in order to remove second factor auth.
The reason for WebAuthn being secondary to TOPT is that in that way,
users will still be able to log in using their code from their phone's
application if they don't have their security keys with them – or maybe
even lost them.
* We had to change a little the flow for setting up TOTP, given that now
it's possible to setting up again if you already had TOTP, in order to
let users modify their authenticator app – given that now it's not
possible for them to disable TOTP and set it up again with another
authenticator app.
So, basically, now instead of storing the new `otp_secret` in the
user, we store it in the session until the process of set up is
finished.
This was because, as it was before, when users clicked on 'Edit' in
the new two-factor methods lists page, but then went back without
finishing the flow, their `otp_secret` had been changed therefore
invalidating their previous authenticator app, making them unable to
log in again using TOTP.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* refactor: fix eslint errors
The PR build was failing given that linting returning some errors.
This commit attempts to fix them.
* refactor: normalize i18n translations
The build was failing given that i18n translations files were not
normalized.
This commits fixes that.
* refactor: avoid having the webauthn gem locked to a specific version
* refactor: use symbols for routes without '/'
* refactor: avoid sending webauthn disabled email when 2FA is disabled
When an admins disable 2FA for users, we were sending two mails
to them, one notifying that 2FA was disabled and the other to notify
that WebAuthn was disabled.
As the second one is redundant since the first email includes it, we can
remove it and send just one email to users.
* refactor: avoid creating new env variable for webauthn_origin config
* refactor: improve flash error messages for webauthn pages
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
2020-08-24 15:46:27 +01:00
|
|
|
def webauthn_options
|
2021-09-30 04:26:29 +01:00
|
|
|
user = User.find_by(id: session[:attempt_user_id])
|
Add WebAuthn as an alternative 2FA method (#14466)
* feat: add possibility of adding WebAuthn security keys to use as 2FA
This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor
to the Settings page for editing the 2FA methods – now it will list the
methods that are available to the user (TOTP and WebAuthn) and from
there they'll be able to add or remove any of them.
Also, it's worth mentioning that for enabling WebAuthn it's required to
have TOTP enabled, so the first time that you go to the 2FA Settings
page, you'll be asked to set it up.
This work was inspired by the one donde by Github in their platform, and
despite it could be approached in different ways, we decided to go with
this one given that we feel that this gives a great UX.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: add request for WebAuthn as second factor at login if enabled
This commits adds the feature for using WebAuthn as a second factor for
login when enabled.
If users have WebAuthn enabled, now a page requesting for the use of a
WebAuthn credential for log in will appear, although a link redirecting
to the old page for logging in using a two-factor code will also be
present.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: add possibility of deleting WebAuthn Credentials
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: disable WebAuthn when an Admin disables 2FA for a user
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: remove ability to disable TOTP leaving only WebAuthn as 2FA
Following examples form other platforms like Github, we decided to make
Webauthn 2FA secondary to 2FA with TOTP, so that we removed the
possibility of removing TOTP authentication only, leaving users with
just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA'
in order to remove second factor auth.
The reason for WebAuthn being secondary to TOPT is that in that way,
users will still be able to log in using their code from their phone's
application if they don't have their security keys with them – or maybe
even lost them.
* We had to change a little the flow for setting up TOTP, given that now
it's possible to setting up again if you already had TOTP, in order to
let users modify their authenticator app – given that now it's not
possible for them to disable TOTP and set it up again with another
authenticator app.
So, basically, now instead of storing the new `otp_secret` in the
user, we store it in the session until the process of set up is
finished.
This was because, as it was before, when users clicked on 'Edit' in
the new two-factor methods lists page, but then went back without
finishing the flow, their `otp_secret` had been changed therefore
invalidating their previous authenticator app, making them unable to
log in again using TOTP.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* refactor: fix eslint errors
The PR build was failing given that linting returning some errors.
This commit attempts to fix them.
* refactor: normalize i18n translations
The build was failing given that i18n translations files were not
normalized.
This commits fixes that.
* refactor: avoid having the webauthn gem locked to a specific version
* refactor: use symbols for routes without '/'
* refactor: avoid sending webauthn disabled email when 2FA is disabled
When an admins disable 2FA for users, we were sending two mails
to them, one notifying that 2FA was disabled and the other to notify
that WebAuthn was disabled.
As the second one is redundant since the first email includes it, we can
remove it and send just one email to users.
* refactor: avoid creating new env variable for webauthn_origin config
* refactor: improve flash error messages for webauthn pages
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
2020-08-24 15:46:27 +01:00
|
|
|
|
2021-06-21 16:07:30 +01:00
|
|
|
if user&.webauthn_enabled?
|
2021-08-26 15:51:22 +01:00
|
|
|
options_for_get = WebAuthn::Credential.options_for_get(
|
|
|
|
allow: user.webauthn_credentials.pluck(:external_id),
|
|
|
|
user_verification: 'discouraged'
|
|
|
|
)
|
Add WebAuthn as an alternative 2FA method (#14466)
* feat: add possibility of adding WebAuthn security keys to use as 2FA
This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor
to the Settings page for editing the 2FA methods – now it will list the
methods that are available to the user (TOTP and WebAuthn) and from
there they'll be able to add or remove any of them.
Also, it's worth mentioning that for enabling WebAuthn it's required to
have TOTP enabled, so the first time that you go to the 2FA Settings
page, you'll be asked to set it up.
This work was inspired by the one donde by Github in their platform, and
despite it could be approached in different ways, we decided to go with
this one given that we feel that this gives a great UX.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: add request for WebAuthn as second factor at login if enabled
This commits adds the feature for using WebAuthn as a second factor for
login when enabled.
If users have WebAuthn enabled, now a page requesting for the use of a
WebAuthn credential for log in will appear, although a link redirecting
to the old page for logging in using a two-factor code will also be
present.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: add possibility of deleting WebAuthn Credentials
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: disable WebAuthn when an Admin disables 2FA for a user
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: remove ability to disable TOTP leaving only WebAuthn as 2FA
Following examples form other platforms like Github, we decided to make
Webauthn 2FA secondary to 2FA with TOTP, so that we removed the
possibility of removing TOTP authentication only, leaving users with
just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA'
in order to remove second factor auth.
The reason for WebAuthn being secondary to TOPT is that in that way,
users will still be able to log in using their code from their phone's
application if they don't have their security keys with them – or maybe
even lost them.
* We had to change a little the flow for setting up TOTP, given that now
it's possible to setting up again if you already had TOTP, in order to
let users modify their authenticator app – given that now it's not
possible for them to disable TOTP and set it up again with another
authenticator app.
So, basically, now instead of storing the new `otp_secret` in the
user, we store it in the session until the process of set up is
finished.
This was because, as it was before, when users clicked on 'Edit' in
the new two-factor methods lists page, but then went back without
finishing the flow, their `otp_secret` had been changed therefore
invalidating their previous authenticator app, making them unable to
log in again using TOTP.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* refactor: fix eslint errors
The PR build was failing given that linting returning some errors.
This commit attempts to fix them.
* refactor: normalize i18n translations
The build was failing given that i18n translations files were not
normalized.
This commits fixes that.
* refactor: avoid having the webauthn gem locked to a specific version
* refactor: use symbols for routes without '/'
* refactor: avoid sending webauthn disabled email when 2FA is disabled
When an admins disable 2FA for users, we were sending two mails
to them, one notifying that 2FA was disabled and the other to notify
that WebAuthn was disabled.
As the second one is redundant since the first email includes it, we can
remove it and send just one email to users.
* refactor: avoid creating new env variable for webauthn_origin config
* refactor: improve flash error messages for webauthn pages
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
2020-08-24 15:46:27 +01:00
|
|
|
|
|
|
|
session[:webauthn_challenge] = options_for_get.challenge
|
|
|
|
|
2023-02-20 02:16:40 +00:00
|
|
|
render json: options_for_get, status: 200
|
Add WebAuthn as an alternative 2FA method (#14466)
* feat: add possibility of adding WebAuthn security keys to use as 2FA
This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor
to the Settings page for editing the 2FA methods – now it will list the
methods that are available to the user (TOTP and WebAuthn) and from
there they'll be able to add or remove any of them.
Also, it's worth mentioning that for enabling WebAuthn it's required to
have TOTP enabled, so the first time that you go to the 2FA Settings
page, you'll be asked to set it up.
This work was inspired by the one donde by Github in their platform, and
despite it could be approached in different ways, we decided to go with
this one given that we feel that this gives a great UX.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: add request for WebAuthn as second factor at login if enabled
This commits adds the feature for using WebAuthn as a second factor for
login when enabled.
If users have WebAuthn enabled, now a page requesting for the use of a
WebAuthn credential for log in will appear, although a link redirecting
to the old page for logging in using a two-factor code will also be
present.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: add possibility of deleting WebAuthn Credentials
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: disable WebAuthn when an Admin disables 2FA for a user
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: remove ability to disable TOTP leaving only WebAuthn as 2FA
Following examples form other platforms like Github, we decided to make
Webauthn 2FA secondary to 2FA with TOTP, so that we removed the
possibility of removing TOTP authentication only, leaving users with
just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA'
in order to remove second factor auth.
The reason for WebAuthn being secondary to TOPT is that in that way,
users will still be able to log in using their code from their phone's
application if they don't have their security keys with them – or maybe
even lost them.
* We had to change a little the flow for setting up TOTP, given that now
it's possible to setting up again if you already had TOTP, in order to
let users modify their authenticator app – given that now it's not
possible for them to disable TOTP and set it up again with another
authenticator app.
So, basically, now instead of storing the new `otp_secret` in the
user, we store it in the session until the process of set up is
finished.
This was because, as it was before, when users clicked on 'Edit' in
the new two-factor methods lists page, but then went back without
finishing the flow, their `otp_secret` had been changed therefore
invalidating their previous authenticator app, making them unable to
log in again using TOTP.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* refactor: fix eslint errors
The PR build was failing given that linting returning some errors.
This commit attempts to fix them.
* refactor: normalize i18n translations
The build was failing given that i18n translations files were not
normalized.
This commits fixes that.
* refactor: avoid having the webauthn gem locked to a specific version
* refactor: use symbols for routes without '/'
* refactor: avoid sending webauthn disabled email when 2FA is disabled
When an admins disable 2FA for users, we were sending two mails
to them, one notifying that 2FA was disabled and the other to notify
that WebAuthn was disabled.
As the second one is redundant since the first email includes it, we can
remove it and send just one email to users.
* refactor: avoid creating new env variable for webauthn_origin config
* refactor: improve flash error messages for webauthn pages
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
2020-08-24 15:46:27 +01:00
|
|
|
else
|
2023-02-20 02:16:40 +00:00
|
|
|
render json: { error: t('webauthn_credentials.not_enabled') }, status: 401
|
Add WebAuthn as an alternative 2FA method (#14466)
* feat: add possibility of adding WebAuthn security keys to use as 2FA
This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor
to the Settings page for editing the 2FA methods – now it will list the
methods that are available to the user (TOTP and WebAuthn) and from
there they'll be able to add or remove any of them.
Also, it's worth mentioning that for enabling WebAuthn it's required to
have TOTP enabled, so the first time that you go to the 2FA Settings
page, you'll be asked to set it up.
This work was inspired by the one donde by Github in their platform, and
despite it could be approached in different ways, we decided to go with
this one given that we feel that this gives a great UX.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: add request for WebAuthn as second factor at login if enabled
This commits adds the feature for using WebAuthn as a second factor for
login when enabled.
If users have WebAuthn enabled, now a page requesting for the use of a
WebAuthn credential for log in will appear, although a link redirecting
to the old page for logging in using a two-factor code will also be
present.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: add possibility of deleting WebAuthn Credentials
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: disable WebAuthn when an Admin disables 2FA for a user
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* feat: remove ability to disable TOTP leaving only WebAuthn as 2FA
Following examples form other platforms like Github, we decided to make
Webauthn 2FA secondary to 2FA with TOTP, so that we removed the
possibility of removing TOTP authentication only, leaving users with
just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA'
in order to remove second factor auth.
The reason for WebAuthn being secondary to TOPT is that in that way,
users will still be able to log in using their code from their phone's
application if they don't have their security keys with them – or maybe
even lost them.
* We had to change a little the flow for setting up TOTP, given that now
it's possible to setting up again if you already had TOTP, in order to
let users modify their authenticator app – given that now it's not
possible for them to disable TOTP and set it up again with another
authenticator app.
So, basically, now instead of storing the new `otp_secret` in the
user, we store it in the session until the process of set up is
finished.
This was because, as it was before, when users clicked on 'Edit' in
the new two-factor methods lists page, but then went back without
finishing the flow, their `otp_secret` had been changed therefore
invalidating their previous authenticator app, making them unable to
log in again using TOTP.
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
* refactor: fix eslint errors
The PR build was failing given that linting returning some errors.
This commit attempts to fix them.
* refactor: normalize i18n translations
The build was failing given that i18n translations files were not
normalized.
This commits fixes that.
* refactor: avoid having the webauthn gem locked to a specific version
* refactor: use symbols for routes without '/'
* refactor: avoid sending webauthn disabled email when 2FA is disabled
When an admins disable 2FA for users, we were sending two mails
to them, one notifying that 2FA was disabled and the other to notify
that WebAuthn was disabled.
As the second one is redundant since the first email includes it, we can
remove it and send just one email to users.
* refactor: avoid creating new env variable for webauthn_origin config
* refactor: improve flash error messages for webauthn pages
Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
2020-08-24 15:46:27 +01:00
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2016-09-26 22:55:21 +01:00
|
|
|
protected
|
|
|
|
|
2019-09-24 03:35:36 +01:00
|
|
|
def find_user
|
2021-08-25 21:52:41 +01:00
|
|
|
if user_params[:email].present?
|
|
|
|
find_user_from_params
|
|
|
|
elsif session[:attempt_user_id]
|
2020-11-12 22:05:01 +00:00
|
|
|
User.find_by(id: session[:attempt_user_id])
|
2019-09-24 03:35:36 +01:00
|
|
|
end
|
|
|
|
end
|
|
|
|
|
2021-08-25 21:52:41 +01:00
|
|
|
def find_user_from_params
|
|
|
|
user = User.authenticate_with_ldap(user_params) if Devise.ldap_authentication
|
|
|
|
user ||= User.authenticate_with_pam(user_params) if Devise.pam_authentication
|
|
|
|
user ||= User.find_for_authentication(email: user_params[:email])
|
|
|
|
user
|
|
|
|
end
|
|
|
|
|
2017-01-28 19:43:38 +00:00
|
|
|
def user_params
|
2022-04-06 19:58:12 +01:00
|
|
|
params.require(:user).permit(:email, :password, :otp_attempt, credential: {})
|
2017-01-27 19:28:46 +00:00
|
|
|
end
|
|
|
|
|
2017-05-26 13:14:03 +01:00
|
|
|
def after_sign_in_path_for(resource)
|
2016-10-03 15:38:22 +01:00
|
|
|
last_url = stored_location_for(:user)
|
|
|
|
|
2017-05-26 13:14:03 +01:00
|
|
|
if home_paths(resource).include?(last_url)
|
2016-10-03 15:38:22 +01:00
|
|
|
root_path
|
|
|
|
else
|
|
|
|
last_url || root_path
|
|
|
|
end
|
2016-09-26 22:55:21 +01:00
|
|
|
end
|
2017-01-28 19:43:38 +00:00
|
|
|
|
2020-05-10 09:16:39 +01:00
|
|
|
def require_no_authentication
|
|
|
|
super
|
2020-11-12 22:05:01 +00:00
|
|
|
|
2020-05-10 09:16:39 +01:00
|
|
|
# Delete flash message that isn't entirely useful and may be confusing in
|
|
|
|
# most cases because /web doesn't display/clear flash messages.
|
|
|
|
flash.delete(:alert) if flash[:alert] == I18n.t('devise.failure.already_authenticated')
|
|
|
|
end
|
|
|
|
|
2017-05-26 13:14:03 +01:00
|
|
|
private
|
|
|
|
|
2024-09-18 09:05:25 +01:00
|
|
|
def check_suspicious!
|
|
|
|
user = find_user
|
|
|
|
@login_is_suspicious = suspicious_sign_in?(user) unless user.nil?
|
|
|
|
end
|
|
|
|
|
2017-05-26 13:14:03 +01:00
|
|
|
def home_paths(resource)
|
2023-07-24 15:06:32 +01:00
|
|
|
paths = [about_path, '/explore']
|
2020-11-12 22:05:01 +00:00
|
|
|
|
2023-02-18 11:37:47 +00:00
|
|
|
paths << short_account_path(username: resource.account) if single_user_mode? && resource.is_a?(User)
|
2020-11-12 22:05:01 +00:00
|
|
|
|
2017-05-26 13:14:03 +01:00
|
|
|
paths
|
|
|
|
end
|
2018-09-07 04:42:16 +01:00
|
|
|
|
2018-09-09 03:10:44 +01:00
|
|
|
def continue_after?
|
|
|
|
truthy_param?(:continue)
|
|
|
|
end
|
2020-11-12 22:05:01 +00:00
|
|
|
|
|
|
|
def restart_session
|
|
|
|
clear_attempt_from_session
|
|
|
|
redirect_to new_user_session_path, alert: I18n.t('devise.failure.timeout')
|
|
|
|
end
|
|
|
|
|
2023-07-12 09:03:19 +01:00
|
|
|
def register_attempt_in_session(user)
|
2020-11-12 22:05:01 +00:00
|
|
|
session[:attempt_user_id] = user.id
|
|
|
|
session[:attempt_user_updated_at] = user.updated_at.to_s
|
|
|
|
end
|
|
|
|
|
|
|
|
def clear_attempt_from_session
|
|
|
|
session.delete(:attempt_user_id)
|
|
|
|
session.delete(:attempt_user_updated_at)
|
|
|
|
end
|
2021-06-21 16:07:30 +01:00
|
|
|
|
2024-01-19 12:19:49 +00:00
|
|
|
def clear_2fa_attempt_from_user(user)
|
|
|
|
redis.del(second_factor_attempts_key(user))
|
|
|
|
end
|
|
|
|
|
|
|
|
def check_second_factor_rate_limits(user)
|
|
|
|
attempts, = redis.multi do |multi|
|
|
|
|
multi.incr(second_factor_attempts_key(user))
|
|
|
|
multi.expire(second_factor_attempts_key(user), 1.hour)
|
|
|
|
end
|
|
|
|
|
|
|
|
attempts >= MAX_2FA_ATTEMPTS_PER_HOUR
|
|
|
|
end
|
|
|
|
|
2021-06-21 16:07:30 +01:00
|
|
|
def on_authentication_success(user, security_measure)
|
|
|
|
@on_authentication_success_called = true
|
|
|
|
|
2024-01-19 12:19:49 +00:00
|
|
|
clear_2fa_attempt_from_user(user)
|
2021-06-21 16:07:30 +01:00
|
|
|
clear_attempt_from_session
|
|
|
|
|
2022-01-16 12:23:50 +00:00
|
|
|
user.update_sign_in!(new_sign_in: true)
|
2021-06-21 16:07:30 +01:00
|
|
|
sign_in(user)
|
|
|
|
flash.delete(:notice)
|
|
|
|
|
|
|
|
LoginActivity.create(
|
|
|
|
user: user,
|
|
|
|
success: true,
|
|
|
|
authentication_method: security_measure,
|
|
|
|
ip: request.remote_ip,
|
|
|
|
user_agent: request.user_agent
|
|
|
|
)
|
2022-04-06 19:58:12 +01:00
|
|
|
|
2022-06-21 14:16:22 +01:00
|
|
|
UserMailer.suspicious_sign_in(user, request.remote_ip, request.user_agent, Time.now.utc).deliver_later! if @login_is_suspicious
|
2022-04-06 19:58:12 +01:00
|
|
|
end
|
|
|
|
|
|
|
|
def suspicious_sign_in?(user)
|
|
|
|
SuspiciousSignInDetector.new(user).suspicious?(request)
|
2021-06-21 16:07:30 +01:00
|
|
|
end
|
|
|
|
|
|
|
|
def on_authentication_failure(user, security_measure, failure_reason)
|
|
|
|
LoginActivity.create(
|
|
|
|
user: user,
|
|
|
|
success: false,
|
|
|
|
authentication_method: security_measure,
|
|
|
|
failure_reason: failure_reason,
|
|
|
|
ip: request.remote_ip,
|
|
|
|
user_agent: request.user_agent
|
|
|
|
)
|
2024-01-22 13:55:43 +00:00
|
|
|
|
|
|
|
# Only send a notification email every hour at most
|
2024-02-07 11:52:38 +00:00
|
|
|
return if redis.get("2fa_failure_notification:#{user.id}").present?
|
|
|
|
|
|
|
|
redis.set("2fa_failure_notification:#{user.id}", '1', ex: 1.hour)
|
2024-01-22 13:55:43 +00:00
|
|
|
|
|
|
|
UserMailer.failed_2fa(user, request.remote_ip, request.user_agent, Time.now.utc).deliver_later!
|
2021-06-21 16:07:30 +01:00
|
|
|
end
|
2024-01-19 12:19:49 +00:00
|
|
|
|
|
|
|
def second_factor_attempts_key(user)
|
|
|
|
"2fa_auth_attempts:#{user.id}:#{Time.now.utc.hour}"
|
|
|
|
end
|
2024-08-13 18:49:23 +01:00
|
|
|
|
|
|
|
def respond_to_on_destroy
|
|
|
|
respond_to do |format|
|
|
|
|
format.json do
|
|
|
|
render json: {
|
|
|
|
redirect_to: after_sign_out_path_for(resource_name),
|
|
|
|
}, status: 200
|
|
|
|
end
|
|
|
|
format.all { super }
|
|
|
|
end
|
|
|
|
end
|
2016-03-05 21:43:05 +00:00
|
|
|
end
|