Look in config/initializers/devise.rb. There are a lot of configuration settings including config.timeout_in. The default in my version is 30 minutes. You can also set it on the model itself: class User < ActiveRecord::Base devise :timeoutable, :timeout_in => 15.minutes You can now also set the timeout dynamically.
Probably the easiest way to do this is to Define each message as a blank string Check the length of the string before you show a flash message. In your devise.en.yml file, specify each message as empty: en: errors: messages: not_found: ” already_confirmed: ” not_locked: ” etc. Next, in your layout, check for blank flash … Read more
Add devise to your application Gemfile and install it by running bundle install. After this, you should run the following generator command: rails generate devise:install This generator will install an initializer your_application/config/initializers/devise.rb which consists of all the Devise’s configuration options. You missed the above mentioned step which is why the devise configurations are not set … Read more
As suggested here, the following will suffice: <%= link_to “Sign Out”, destroy_user_session_path, data: { “turbo-method”: :delete } %> I have tested this in my project and it seems to work fine. Thanks also to @alexts, you basically figured this out too, however the comment on GitHub even eliminated the double-request.
You could add the following to your rails_helper: RSpec.configure do |config| config.include Devise::Test::ControllerHelpers, type: :controller end This will include Devise::Test::ControllerHelpers module in all :controller specs.
Yes you can do that, when running the generator skip the user model creation: rails generate active_admin:install –skip-users Then in your config/initializers/active_admin.rb : # == User Authentication # # Active Admin will automatically call an authentication # method in a before filter of all controller actions to # ensure that there is a currently logged … Read more
Check the code in app/views/devise/mailer/reset_password_instructions.html.erb The link should be generated with: edit_password_url(@resource, :reset_password_token => @token) If your view still uses this code, that will be the cause of the issue: edit_password_url(@resource, :reset_password_token => @resource.password_reset_token) Devise started storing hashes of the token, so the email needs to create the link using the real token (@token) rather … Read more
This gem works well: https://github.com/devise-security/devise-security Add to Gemfile gem ‘devise-security’ after bundle install rails generate devise_security:install Then run rails g migration AddSessionLimitableToUsers unique_session_id Edit the migration file class AddSessionLimitableToUsers < ActiveRecord::Migration def change add_column :users, :unique_session_id, :string, limit: 20 end end Then run rake db:migrate Edit your app/models/user.rb file class User < ActiveRecord::Base devise :session_limitable … Read more
Here’s one way I was able to do it: >> ApplicationController.allow_forgery_protection = false >> app.post(‘/sign_in’, {“user”=>{“login”=>”login”, “password”=>”password”}}) Then you can do: >> app.get ‘/some_other_path_that_only_works_if_logged_in’ >> pp app.response.body
You can subclass the controller and configure the router to use that: class SessionsController < Devise::SessionsController layout false end And in config/routes.rb: devise_for :users, :controllers => { :sessions => “sessions” } You need to move the session views to this controller too. OR make a method in app/controllers/application_controller.rb: class ApplicationController < ActionController::Base layout :layout private … Read more