Rails 4.2 : ActionView::Template::Error (undefined method `model_name' for #<UserSession: no credentials provided>)

[aurels]

Hello,

I'm migrating my app from Rails 4.1 to 4.2, with AuthLogic version 3.4.2.

When visiting the login page, I get this error in the view :

undefined method `model_name' for #<UserSession: no credentials provided>

Here is the associated controller :

class UserSessionsController < ApplicationController

  layout 'login'

  before_action :login_required,    :only => [:destroy]
  before_action :no_login_required, :only => [:new, :create]

  def new
    @user_session = UserSession.new
  end

  ...
end

And the session model is empty :

# coding: UTF-8

class UserSession < Authlogic::Session::Base
end

And the user model :

acts_as_authentic do |config|
    config.maintain_sessions = true
    config.merge_validates_length_of_password_field_options({ :minimum => 8 })
end

Any idea ? Thanks.

[codeodor]

I thought Rails went to requiring ActiveModel::Naming-compliant objects for forms and links a long time ago, but I guess not because I'm getting the same error.

Until a proper fix is released in AuthLogic, you can use this, which seems to have worked for me:

class UserSession < Authlogic::Session::Base
  include ActiveModel::Naming
  def parents
    []
  end

  def name
    "UserSession"
  end
end

Caveat: I still have a bunch of errors to work through, but this removed the error on the login form for my app. No idea if logging in actually works because other errors are preventing the pages from loading. 😄

[codeodor]

So I'm not sure if that's all that is needed. Trying to log in now, and it seems like none of my passwords are matching. But I'm updating from an app that started life in Rails 1.x, and its latest version is being updated from 3.2 to 4.2.

[aurels]

Hi @codeodor,

I'll try that ASAP and tell if I have other issues.

It's an old app we have been migrating too. From Rails 2.0 to 2.2, then to 3.0, then to 3.2, then to 4. And now to 4.2.

[aurels]

Yep it does fix the login page and the passwords are matching. I did not test the other features yet, I'll let you know if Authlogic fully works on 4.2 for me.

Thanks again !

[codeodor]

@bwlang I think class.name might be a better general purpose name for use inside Authlogic, since people can name their implemented classes other than UserSession

(mentioned in case you're making that a pull request)

[konung]

That fixed the same problem for me on an app that is being upgraded from 3.2 to 4.2

[tiegz]

@aurels @codeodor curious if you could try another solution too... does it work with default Authlogic if you set config.eager_load = true in config/environments/development.rb?

[tiegz]

( @codeodor the password matching thing could be because the default crypto provider changed to SCrypt. I might try to make the messaging more obvious in README: 33dca9e)

[bwlang]

I'm running the 4.2 code suggested by codeodor in production now... seems solid.
I have not run the test suite yet, but once I do I'll issue a pull request.

[codeodor]

@tiegz My tests were giving errors, so I enabled eager_load in that environment and removed my patch on UserSession. Unfortunately, the error persisted, so setting config.eager_load to true does not seem to fix the issue.

[aurels]

@tiegz No it doesn't work with in config/environments/development.rb?, and I don't see why it would ;-)

[codeodor]

@tiegz Thanks for the tip about the password matching. I enabled migration and it worked like a charm!

[orien]

This fixed the problem for me:

class UserSession < Authlogic::Session::Base
  extend ActiveModel::Naming
end

[codeodor]

@orien Of course! Why didn't I think of that? 😁 That's a much better solution.

[cpg]

With the Rails 4.2 release out, this is starting to hit more and more authlogic-based apps.

Is what @orien suggested a safe work-around? (seems to be working well for my app)

[tiegz]

I've just pushed a commit to fix this (and cleanup some old methods)... wfm in a new Rails 4.2 app. If anyone else can confirm, I'll update the gem too:

0e66c86

[codeodor]

@cpg Yes, that solution is safe and works. However, the update to this repo from @tiegz is better, since it's going to make it into the gem. :)

@tiegz I can confirm that commit fixes the issue I was seeing here.

[cpg]

@tiegz I can also confirm that the pushed changes [1]appear to work well after removing the extend work-around above from my app.

[1] i.e. deploying from git@github.com:binarylogic/authlogic.git

[tiegz]

Ok, thanks everyone! Just pushed the v3.4.4 gem:

https://github.com/binarylogic/authlogic/tree/v3.4.4

[codeodor]

Awesome, thanks! 👍

[cpg]

Did a deployment wit the official gem and basic login/logout seems to work fine. Thanks and great job.