Module: Devise::Models::Authenticatable
- Extended by:
- ActiveSupport::Concern
- Defined in:
- lib/devise/models/authenticatable.rb
Overview
Authenticatable module. Holds common settings for authentication.
Options
Authenticatable adds the following options to devise_for:
* +authentication_keys+: parameters used for authentication. By default [:email].
* +http_authentication_key+: map the username passed via HTTP Auth to this parameter. Defaults to
the first element in +authentication_keys+.
* +request_keys+: parameters from the request object used for authentication.
By a symbol (which should be a request method), it will automatically be
passed to find_for_authentication method and considered in your model lookup.
For instance, if you set :request_keys to [:subdomain], :subdomain will be considered
as key on authentication. This can also be a hash where the value is a boolean
if the value is required or not.
* +http_authenticatable+: if this model allows http authentication. By default false.
It also accepts an array the strategies that should allow http.
* +params_authenticatable+: if this model allows authentication through request params. By default true.
It also accepts an array the strategies that should allow params authentication.
* +skip_session_storage+: By default Devise will store the user in session.
You can skip storage for http and token auth by appending values to array:
:skip_session_storage => [:token_auth] or :skip_session_storage => [:http_auth, :token_auth],
by default is set to :skip_session_storage => [:http_auth].
active_for_authentication?
After authenticating a user and in each request, Devise checks if your model is active by calling model.active_for_authentication?. This method is overwritten by other devise modules. For instance, :confirmable overwrites .active_for_authentication? to only return true if your model was confirmed.
You overwrite this method yourself, but if you do, don’t forget to call super:
def active_for_authentication?
super && special_condition_is_valid?
end
Whenever active_for_authentication? returns false, Devise asks the reason why your model is inactive using the inactive_message method. You can overwrite it as well:
def
special_condition_is_valid? ? super : :special_condition_is_not_valid
end
Defined Under Namespace
Modules: ClassMethods
Constant Summary collapse
- BLACKLIST_FOR_SERIALIZATION =
[:encrypted_password, :reset_password_token, :reset_password_sent_at, :remember_created_at, :sign_in_count, :current_sign_in_at, :last_sign_in_at, :current_sign_in_ip, :last_sign_in_ip, :password_salt, :confirmation_token, :confirmed_at, :confirmation_sent_at, :remember_token, :unconfirmed_email, :failed_attempts, :unlock_token, :locked_at, :authentication_token]
Class Method Summary collapse
Instance Method Summary collapse
- #active_for_authentication? ⇒ Boolean
- #apply_to_attribute_or_variable(attr, method) ⇒ Object protected
- #authenticatable_salt ⇒ Object
- #devise_mailer ⇒ Object protected
- #downcase_keys ⇒ Object protected
- #inactive_message ⇒ Object
-
#send_devise_notification(notification, *args) ⇒ Object
protected
This is an internal method called every time Devise needs to send a notification/mail.
- #strip_whitespace ⇒ Object protected
- #unauthenticated_message ⇒ Object
-
#valid_for_authentication? ⇒ Boolean
Check if the current object is valid for authentication.
Class Method Details
.required_fields(klass) ⇒ Object
71 72 73 |
# File 'lib/devise/models/authenticatable.rb', line 71 def self.required_fields(klass) [] end |
Instance Method Details
#active_for_authentication? ⇒ Boolean
89 90 91 |
# File 'lib/devise/models/authenticatable.rb', line 89 def active_for_authentication? true end |
#apply_to_attribute_or_variable(attr, method) ⇒ Object (protected)
186 187 188 189 190 191 192 193 194 195 196 197 |
# File 'lib/devise/models/authenticatable.rb', line 186 def apply_to_attribute_or_variable(attr, method) if self[attr] self[attr].try(method) # Use respond_to? here to avoid a regression where globally # configured strip_whitespace_keys or case_insensitive_keys were # attempting to strip! or downcase! when a model didn't have the # globally configured key. elsif respond_to?(attr) send(attr).try(method) end end |
#authenticatable_salt ⇒ Object
97 98 |
# File 'lib/devise/models/authenticatable.rb', line 97 def authenticatable_salt end |
#devise_mailer ⇒ Object (protected)
127 128 129 |
# File 'lib/devise/models/authenticatable.rb', line 127 def devise_mailer Devise.mailer end |
#downcase_keys ⇒ Object (protected)
178 179 180 |
# File 'lib/devise/models/authenticatable.rb', line 178 def downcase_keys self.class.case_insensitive_keys.each { |k| apply_to_attribute_or_variable(k, :downcase!) } end |
#inactive_message ⇒ Object
93 94 95 |
# File 'lib/devise/models/authenticatable.rb', line 93 def :inactive end |
#send_devise_notification(notification, *args) ⇒ Object (protected)
This is an internal method called every time Devise needs to send a notification/mail. This can be overriden if you need to customize the e-mail delivery logic. For instance, if you are using a queue to deliver e-mails (delayed job, sidekiq, resque, etc), you must add the delivery to the queue just after the transaction was committed. To achieve this, you can override send_devise_notification to store the deliveries until the after_commit callback is triggered:
class User
devise :database_authenticatable, :confirmable
after_commit :send_pending_notifications
protected
def send_devise_notification(notification, *args)
# If the record is new or changed then delay the
# delivery until the after_commit callback otherwise
# send now because after_commit will not be called.
if new_record? || changed?
pending_notifications << [notification, args]
else
devise_mailer.send(notification, self, *args).deliver
end
end
def send_pending_notifications
pending_notifications.each do |notification, args|
devise_mailer.send(notification, self, *args).deliver
end
# Empty the pending notifications array because the
# after_commit hook can be called multiple times which
# could cause multiple emails to be sent.
pending_notifications.clear
end
def pending_notifications
@pending_notifications ||= []
end
end
174 175 176 |
# File 'lib/devise/models/authenticatable.rb', line 174 def send_devise_notification(notification, *args) devise_mailer.send(notification, self, *args).deliver end |
#strip_whitespace ⇒ Object (protected)
182 183 184 |
# File 'lib/devise/models/authenticatable.rb', line 182 def strip_whitespace self.class.strip_whitespace_keys.each { |k| apply_to_attribute_or_variable(k, :strip!) } end |
#unauthenticated_message ⇒ Object
85 86 87 |
# File 'lib/devise/models/authenticatable.rb', line 85 def :invalid end |
#valid_for_authentication? ⇒ Boolean
Check if the current object is valid for authentication. This method and find_for_authentication are the methods used in a Warden::Strategy to check if a model should be signed in or not.
However, you should not overwrite this method, you should overwrite active_for_authentication? and inactive_message instead.
81 82 83 |
# File 'lib/devise/models/authenticatable.rb', line 81 def valid_for_authentication? block_given? ? yield : true end |