karmi
signed_in? returns false
Hi, signed_in? keeps returning false always. Is this because of lack of updates to the gem or something? Thanks @karmi :)
Hi @steverob, yes, that might well be, I don't even remember the repository :) I'd like to help you, but it's really ancient, I think you'll have to dig yourself...
Haha :) thanks @karmi. I was thinking the same thing and I'm gonna update this for the latest clearance :)
Regards Steve Robinson
On Jul 12, 2016, at 9:43 PM, Karel Minarik [email protected] wrote:
Hi @steverob, yes, that might well be, I don't even remember the repository :) I'd like to help you, but it's really ancient, I think you'll have to dig yourself...
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
@karmi so weird -
This gives 401 even if env[:clearance].signed_in? returns true.
@jgarth I am working on your fork only - #1 :) Do share your thoughts. This passes with your dummy test app though - which is the weirdest part. And my Rails app is 4.2 though. Any updates to Rack::Auth?
Thanks!!
Hey @steverob, sorry to disappoint but I haven't used clearance (and clearance_http_auth) in four years… no idea why it's not working anymore. Good luck :)
Haha :) sure sure. Just curious, you guys still using rails or moved on?
Regards Steve Robinson
On Jul 13, 2016, at 9:05 PM, Joachim Garth [email protected] wrote:
Hey @steverob, sorry to disappoint but I haven't used clearance (and clearance_http_auth) in four years… no idea why it's not working anymore. Good luck :)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Awesome @karmi :)
Regards Steve Robinson
On Jul 13, 2016, at 10:25 PM, Karel Minarik [email protected] wrote:
@steverob Still using Rails for sure! :)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.