Edit Question - KnowledgeHub

Title Body

We have an existing user base and are adding email confirmation. Confirmation is optional but will allow additional features. Users are not required to confirm. I've added the confirmable module and ran migrations. Confirmation works as advertised. But, users cannot log in since they are not confirmed. All current users have nil confirmation values, which is what we want (users can go back and confirm their email at any time). I've followed all the Devise wiki articles and set allow_unconfirmed_access_for in the initializer: config.allow_unconfirmed_access_for = 10.years I've also tried setting it in our user model as well: devise :confirmable, allow_unconfirmed_access_for: 10.years I've also tried using other values (1.year, 500.days, etc.) My SessionsController , which does not differ much from Devise's method ( here on github ) class Users::SessionsController < Devise::SessionsController respond_to :json def new redirect_to "/#login" end def create resource = warden.authenticate(auth_options) if !resource render json: {error: "Invalid email or password" }, status: 401 and return end sign_in(resource_name, resource) render "sign_in", formats: [:json], locals: { object: resource } end end Devise's the response: {"error": "You have to confirm your account before continuing."} Devise 2.1.2 with Rails 3.2.9.

Tags (comma-separated) Cancel