current_user_session.user return nil
Reported by net1957 | March 23rd, 2009 @ 06:40 PM
hello !
I migrated to 2.0.1 gem and have a problem in def current_user :
@current_user = current_user_session && current_user_session.user
current_user_session is a valid record, but current_user_session.user return nil
So no authentication !
the only change was :
update gem to 2.0.1 and change users controller to adapt syntax :
acts_as_authentic do |c|
c.logged_in_timeout = CFG['logged_in_timeout']
end
Any idea ?
it's on rails 2.3.2 and was working with authlogic 1.4.3
Comments and changes to this ticket
-
Ben Johnson March 23rd, 2009 @ 08:06 PM
- State changed from “new” to “open”
That is strange, I have an app working just fine in rails 2.3.2. Can you give me more info?
-
Ben Johnson March 23rd, 2009 @ 08:07 PM
That is strange, I have an app working just fine in rails 2.3.2. Can you give me more info?
-
Brian Lopez March 23rd, 2009 @ 08:09 PM
I have this same issue, but noticed it yesterday sometime when I upgraded to 2.0. I've since upgraded to 2.0.1.
I am also on Rails 2.3.2 and was previously working before upgrading Authlogic.
I did some digging and found what may be a chicken-and-egg problem with Authlogic::Session::Timeout#enforce_timeout and AuthLogic::Session::MagicColumns#set_last_request_at
From what I can tell, the last_request_at field is never set because enforce_timeout is called before it has a chance to. As a result, "record" is set to nil, and then the if statement fails in AuthLogic::Session::MagicColumns#set_last_request_at - preventing it's value from being set.
-
Ben Johnson March 23rd, 2009 @ 08:11 PM
Ahh, good find, I will try to create a test to duplicate this and release a fix.
-
Brian Lopez March 23rd, 2009 @ 08:14 PM
Not sure if this helps at all... But I noticed if I comment out my session timeout settings and complete a successful login. Then, within the same browser session, uncommented that code so session timeouts are re-enabled - I can then login and logout as I'd expect. Then, if I close out my browser session and try to login again, I have the same problem as before.
-
Ben Johnson March 24th, 2009 @ 12:54 AM
- State changed from “open” to “resolved”
I believe I fixed the issue. The problem was that the last_request_at field was not getting updated after a successful login. So the next persistence try would be stale. Anyways, this should be fixed. I am pushing out an update now.
-
-
Luis Fernando da Silva May 19th, 2011 @ 06:49 PM
- Milestone order changed from “0” to “0”
Hi I think I have the same problem, but I am already using a newer version
:patch: 2 :major: 2 :minor: 1
Rails: 2.3.5
I am getting a nil for current_user, after I tried to use the:
acts_as_authentic do |c|c.logged_in_timeout 10.minutesend
class MemberSession < Authlogic::Session::Base
logout_on_timeout true # default if falseadd_column :members, :last_request_at, :datetime
Would it be possible this problem is back?
Here are my methods to get the current_user
def current_user_session
return @current_user_session if defined?(@current_user_session) @current_user_session = MemberSession.find return @current_user_sessionend
def current_user
logger.debug "current_user DEFINED" if defined?(@current_user) return @current_user if defined?(@current_user) logger.debug "current_user NOT DEFINED" @current_user = current_user_session && current_user_session.recordNIL HERE--->logger.debug "CURRENT_USER #{@current_user.name}"
return @current_userend
-
Daz Beres May 20th, 2011 @ 02:06 AM
I seem to be having a problem similar to Luiz's, however I'm running Rails 3.0.1 and Authlogic 2.1.6 - and the error seems to be a recent problem as it was working a couple weeks ago (I wasn't working on this for a little while)
The problem arises when the following is included in the 'authentic' model:
acts_as_authentic do |c|
c.logged_in_timeout = 10.minutesend
and the following in the account_session model:
logout_on_timeout true
-
Luis Fernando da Silva May 20th, 2011 @ 10:48 AM
Hi,
I notice that I have an old version, however I have tested with the latest before rails 3.0, once my rails is 2.3.5, So I tested with version 2.1.6, I was full of hope, but the error is still there.
The problem happens when you activate the logout feature
logout_on_timeout true
Please any comment?
-
chirurgie.maroc.tunisie (at gmail) October 10th, 2017 @ 09:38 AM
https://www.medespoir.fr/
https://www.medespoir.fr/lifting-visage-tunisie/
https://www.medespoir.fr/blepharoplastie-tunisie/
https://www.medespoir.fr/rhinoplastie-tunisie/
https://www.medespoir.fr/injection-botox-tunisie/
https://www.medespoir.fr/acide-hyaluronique-tunisie/
https://www.medespoir.fr/lifting-seins-tunisie/
https://www.medespoir.fr/reduction-mammaire-tunisie/
https://www.medespoir.fr/lipofilling-seins-tunisie/
https://www.medespoir.fr/abdominoplastie-tunisie/
https://www.medespoir.fr/liposuccion-tunisie/
https://www.medespoir.fr/augmentation-fesses-tunisie/
https://www.medespoir.fr/lipofilling-fesses-tunisie/
https://www.medespoir.fr/lifting-cuisses-tunisie/
https://www.medespoir.fr/lifting-bras-tunisie/
https://www.medespoir.fr/implant-dentaire-tunisie/
https://www.medespoir.fr/sleeve-tunisie/
https://www.medespoir.fr/bypass-tunisie/ -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Chirurgie-seins-Tunisie February 19th, 2018 @ 09:28 AM
La chirurgie esthetique en Tunisie propose dans le cadre d'un séjour tout compris la chirurgie bariatrique, la chirurgie des seins ou encore le remodelage de la silhouette.
Les interventions de la chirurgie seins Tunisie les plus demandées sont :
l'augmentation mammaire tunisie
le lipofilling seins tunisie
le lifting seins tunisie
et la réduction mammaire tunisie -
Sleeve gastrectomie tarif tunisie March 1st, 2018 @ 10:12 AM
Faire une liposuccion en Tunisieest une très bonne idée. Autres opérations esthétiques
-
-
-
-
-
-
-
-
-
-
-
-
1721792931_1516076445.jpg
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Object based authentication solution that handles all of the non sense for you. It's as easy as ActiveRecord is with a database.
People watching this ticket
Brian Lopez
Luis Fernando da Silva
Attachments
-
1721792931_1516076445.jpg
117.7 KB
Referenced by
-
64
reset_failed_login_count fail
And thanks for your reactivity for ticket #63
-
119
functional testing witih rails 2.3.2 doesn't work like the documentation says
And it's really from line #63 of the authlogic file.