/config/initializers/devise.rb

  1# Use this hook to configure devise mailer, warden hooks and so forth.
  2# Many of these configuration options can be set straight in your model.
  3Devise.setup do |config|
  4  # The secret key used by Devise. Devise uses this key to generate
  5  # random tokens. Changing this key will render invalid all existing
  6  # confirmation, reset password and unlock tokens in the database.
  7  # config.secret_key = '570dd21b702a3b14913d473df94bb1267adc792638b98b3c4dbb6f909e6f0759253fbbd73129b063be6fcb707622ef7e5f1301a73765952b4e688915d8e9f4ef'
  8
  9  # ==> Mailer Configuration
 10  # Configure the e-mail address which will be shown in Devise::Mailer,
 11  # note that it will be overwritten if you use your own mailer class
 12  # with default "from" parameter.
 13  config.mailer_sender = 'donotreply@limageshare.com'
 14
 15  # Configure the class responsible to send e-mails.
 16  # config.mailer = 'Devise::Mailer'
 17
 18  # ==> ORM configuration
 19  # Load and configure the ORM. Supports :active_record (default) and
 20  # :mongoid (bson_ext recommended) by default. Other ORMs may be
 21  # available as additional gems.
 22  require 'devise/orm/active_record'
 23
 24  # ==> Configuration for any authentication mechanism
 25  # Configure which keys are used when authenticating a user. The default is
 26  # just :email. You can configure it to use [:username, :subdomain], so for
 27  # authenticating a user, both parameters are required. Remember that those
 28  # parameters are used only when authenticating and not when retrieving from
 29  # session. If you need permissions, you should implement that in a before filter.
 30  # You can also supply a hash where the value is a boolean determining whether
 31  # or not authentication should be aborted when the value is not present.
 32  config.authentication_keys = [ :username ]
 33
 34  # Configure parameters from the request object used for authentication. Each entry
 35  # given should be a request method and it will automatically be passed to the
 36  # find_for_authentication method and considered in your model lookup. For instance,
 37  # if you set :request_keys to [:subdomain], :subdomain will be used on authentication.
 38  # The same considerations mentioned for authentication_keys also apply to request_keys.
 39  # config.request_keys = []
 40
 41  # Configure which authentication keys should be case-insensitive.
 42  # These keys will be downcased upon creating or modifying a user and when used
 43  # to authenticate or find a user. Default is :email.
 44  config.case_insensitive_keys = [ :email ]
 45
 46  # Configure which authentication keys should have whitespace stripped.
 47  # These keys will have whitespace before and after removed upon creating or
 48  # modifying a user and when used to authenticate or find a user. Default is :email.
 49  config.strip_whitespace_keys = [ :email ]
 50
 51  # Tell if authentication through request.params is enabled. True by default.
 52  # It can be set to an array that will enable params authentication only for the
 53  # given strategies, for example, `config.params_authenticatable = [:database]` will
 54  # enable it only for database (email + password) authentication.
 55  # config.params_authenticatable = true
 56
 57  # Tell if authentication through HTTP Auth is enabled. False by default.
 58  # It can be set to an array that will enable http authentication only for the
 59  # given strategies, for example, `config.http_authenticatable = [:database]` will
 60  # enable it only for database authentication. The supported strategies are:
 61  # :database      = Support basic authentication with authentication key + password
 62  # config.http_authenticatable = false
 63
 64  # If http headers should be returned for AJAX requests. True by default.
 65  # config.http_authenticatable_on_xhr = true
 66
 67  # The realm used in Http Basic Authentication. 'Application' by default.
 68  # config.http_authentication_realm = 'Application'
 69
 70  # It will change confirmation, password recovery and other workflows
 71  # to behave the same regardless if the e-mail provided was right or wrong.
 72  # Does not affect registerable.
 73  # config.paranoid = true
 74
 75  # By default Devise will store the user in session. You can skip storage for
 76  # particular strategies by setting this option.
 77  # Notice that if you are skipping storage for all authentication paths, you
 78  # may want to disable generating routes to Devise's sessions controller by
 79  # passing skip: :sessions to `devise_for` in your config/routes.rb
 80  config.skip_session_storage = [:http_auth]
 81
 82  # By default, Devise cleans up the CSRF token on authentication to
 83  # avoid CSRF token fixation attacks. This means that, when using AJAX
 84  # requests for sign in and sign up, you need to get a new CSRF token
 85  # from the server. You can disable this option at your own risk.
 86  # config.clean_up_csrf_token_on_authentication = true
 87
 88  # ==> Configuration for :database_authenticatable
 89  # For bcrypt, this is the cost for hashing the password and defaults to 10. If
 90  # using other encryptors, it sets how many times you want the password re-encrypted.
 91  #
 92  # Limiting the stretches to just one in testing will increase the performance of
 93  # your test suite dramatically. However, it is STRONGLY RECOMMENDED to not use
 94  # a value less than 10 in other environments. Note that, for bcrypt (the default
 95  # encryptor), the cost increases exponentially with the number of stretches (e.g.
 96  # a value of 20 is already extremely slow: approx. 60 seconds for 1 calculation).
 97  config.stretches = Rails.env.test? ? 1 : 10
 98
 99  # Setup a pepper to generate the encrypted password.
100  # config.pepper = '8221bf61b0a4e9d96d90623d63b27b8a04f333ca7baf304b0f62510d843f74cb06ac4e7c7889004f29852a1d8bb7e50b6063086c329963bc110c0b1a95656490'
101
102  # ==> Configuration for :confirmable
103  # A period that the user is allowed to access the website even without
104  # confirming their account. For instance, if set to 2.days, the user will be
105  # able to access the website for two days without confirming their account,
106  # access will be blocked just in the third day. Default is 0.days, meaning
107  # the user cannot access the website without confirming their account.
108  # config.allow_unconfirmed_access_for = 2.days
109
110  # A period that the user is allowed to confirm their account before their
111  # token becomes invalid. For example, if set to 3.days, the user can confirm
112  # their account within 3 days after the mail was sent, but on the fourth day
113  # their account can't be confirmed with the token any more.
114  # Default is nil, meaning there is no restriction on how long a user can take
115  # before confirming their account.
116  # config.confirm_within = 3.days
117
118  # If true, requires any email changes to be confirmed (exactly the same way as
119  # initial account confirmation) to be applied. Requires additional unconfirmed_email
120  # db field (see migrations). Until confirmed, new email is stored in
121  # unconfirmed_email column, and copied to email column on successful confirmation.
122  config.reconfirmable = true
123
124  # Defines which key will be used when confirming an account
125  # config.confirmation_keys = [ :email ]
126
127  # ==> Configuration for :rememberable
128  # The time the user will be remembered without asking for credentials again.
129  # config.remember_for = 2.weeks
130
131  # If true, extends the user's remember period when remembered via cookie.
132  # config.extend_remember_period = false
133
134  # Options to be passed to the created cookie. For instance, you can set
135  # secure: true in order to force SSL only cookies.
136  # config.rememberable_options = {}
137
138  # ==> Configuration for :validatable
139  # Range for password length.
140  config.password_length = 8..128
141
142  # Email regex used to validate email formats. It simply asserts that
143  # one (and only one) @ exists in the given string. This is mainly
144  # to give user feedback and not to assert the e-mail validity.
145  # config.email_regexp = /\A[^@]+@[^@]+\z/
146
147  # ==> Configuration for :timeoutable
148  # The time you want to timeout the user session without activity. After this
149  # time the user will be asked for credentials again. Default is 30 minutes.
150  # config.timeout_in = 30.minutes
151
152  # If true, expires auth token on session timeout.
153  # config.expire_auth_token_on_timeout = false
154
155  # ==> Configuration for :lockable
156  # Defines which strategy will be used to lock an account.
157  # :failed_attempts = Locks an account after a number of failed attempts to sign in.
158  # :none            = No lock strategy. You should handle locking by yourself.
159  config.lock_strategy = :failed_attempts
160
161  # Defines which key will be used when locking and unlocking an account
162  config.unlock_keys = [ :email ]
163
164  # Defines which strategy will be used to unlock an account.
165  # :email = Sends an unlock link to the user email
166  # :time  = Re-enables login after a certain amount of time (see :unlock_in below)
167  # :both  = Enables both strategies
168  # :none  = No unlock strategy. You should handle unlocking by yourself.
169  config.unlock_strategy = :email
170
171  # Number of authentication tries before locking an account if lock_strategy
172  # is failed attempts.
173  config.maximum_attempts = 5
174
175  # Time interval to unlock the account if :time is enabled as unlock_strategy.
176  # config.unlock_in = 1.hour
177
178  # Warn on the last attempt before the account is locked.
179  config.last_attempt_warning = true
180
181  # ==> Configuration for :recoverable
182  #
183  # Defines which key will be used when recovering the password for an account
184  config.reset_password_keys = [ :email ]
185
186  # Time interval you can reset your password with a reset password key.
187  # Don't put a too small interval or your users won't have the time to
188  # change their passwords.
189  config.reset_password_within = 6.hours
190
191  # ==> Configuration for :encryptable
192  # Allow you to use another encryption algorithm besides bcrypt (default). You can use
193  # :sha1, :sha512 or encryptors from others authentication tools as :clearance_sha1,
194  # :authlogic_sha512 (then you should set stretches above to 20 for default behavior)
195  # and :restful_authentication_sha1 (then you should set stretches to 10, and copy
196  # REST_AUTH_SITE_KEY to pepper).
197  #
198  # Require the `devise-encryptable` gem when using anything other than bcrypt
199  # config.encryptor = :sha512
200
201  # ==> Scopes configuration
202  # Turn scoped views on. Before rendering "sessions/new", it will first check for
203  # "users/sessions/new". It's turned off by default because it's slower if you
204  # are using only default views.
205  # config.scoped_views = false
206
207  # Configure the default scope given to Warden. By default it's the first
208  # devise role declared in your routes (usually :user).
209  # config.default_scope = :user
210
211  # Set this configuration to false if you want /users/sign_out to sign out
212  # only the current scope. By default, Devise signs out all scopes.
213  # config.sign_out_all_scopes = true
214
215  # ==> Navigation configuration
216  # Lists the formats that should be treated as navigational. Formats like
217  # :html, should redirect to the sign in page when the user does not have
218  # access, but formats like :xml or :json, should return 401.
219  #
220  # If you have any extra navigational formats, like :iphone or :mobile, you
221  # should add them to the navigational formats lists.
222  #
223  # The "*/*" below is required to match Internet Explorer requests.
224  # config.navigational_formats = ['*/*', :html]
225
226  # The default HTTP method used to sign out a resource. Default is :delete.
227  config.sign_out_via = :delete
228
229  # ==> OmniAuth
230  # Add a new OmniAuth provider. Check the wiki for more information on setting
231  # up on your models and hooks.
232  # config.omniauth :github, 'APP_ID', 'APP_SECRET', scope: 'user,public_repo'
233
234  # ==> Warden configuration
235  # If you want to use other strategies, that are not supported by Devise, or
236  # change the failure app, you can configure them inside the config.warden block.
237  #
238  # config.warden do |manager|
239  #   manager.intercept_401 = false
240  #   manager.default_strategies(scope: :user).unshift :some_external_strategy
241  # end
242
243  # ==> Mountable engine configurations
244  # When using Devise inside an engine, let's call it `MyEngine`, and this engine
245  # is mountable, there are some extra configurations to be taken into account.
246  # The following options are available, assuming the engine is mounted as:
247  #
248  #     mount MyEngine, at: '/my_engine'
249  #
250  # The router that invoked `devise_for`, in the example above, would be:
251  # config.router_name = :my_engine
252  #
253  # When using omniauth, Devise cannot automatically set Omniauth path,
254  # so you need to do it manually. For the users scope, it would be:
255  # config.omniauth_path_prefix = '/my_engine/users/auth'
256end