Login problem

4 views
Skip to first unread message

AL

unread,
Mar 18, 2010, 10:30:25 AM3/18/10
to Lipsiadmin
Hello,
I just tried lipsiadmin because I need a solution for the admin part
of a site.
I can not login, I think because of this:
/app/models/account.rb:55: warning: argumtents for
OpenSSL::Cipher::Cipher#encrypt and OpenSSL::Cipher::Cipher#decrypt
were deprecated; use OpenSSL::Cipher::Cipher#pkcs5_keyivgen to derive
key and IV
There is more info on this here:
http://stackoverflow.com/questions/1349397/how-to-resolve-deprecation-warnings-for-opensslciphercipherencrypt
Thanks,
AL

Davide D'Agostino

unread,
Mar 18, 2010, 10:42:58 AM3/18/10
to lipsi...@googlegroups.com
Hi,

Im see warning too (which will be fixed) but Im sure that login work. Im using ruby-p72 and tested also on ruby-p149

> --
> Hai ricevuto questo messaggio perché sei iscritto al gruppo "Lipsiadmin" di Google Gruppi.
> Per postare messaggi in questo gruppo, invia un'email a lipsi...@googlegroups.com.
> Per annullare l'iscrizione a questo gruppo, invia un'email a lipsiadmin+...@googlegroups.com.
> Per ulteriori opzioni, visita il gruppo all'indirizzo http://groups.google.com/group/lipsiadmin?hl=it.
>
>

AL

unread,
Mar 18, 2010, 11:06:50 AM3/18/10
to Lipsiadmin
Hello,
Thanks for your reply.
I'm using ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux] and
Rails 2.3.5
When I first visit /backend I get the login page. After I entered the
email and the password and click login I just get the login page again
with a
"Wrong email or password" message. On the console I have the above
warning and if I visit /backend after that I get the
"No route matches "/backend/base" with {:method=>:get}" error here:
lipsiadmin (5.1.2) lib/access_control/base.rb:105:in
`allow_all_actions'
app/models/account_access.rb:6
I commented out the problematic line (role.allow_all_actions "/backend/
base") for testing and after visiting /backend again
I get the loading page but the app stucked there with the following
errors:
.gem/ruby/1.8/gems/lipsiadmin-5.1.2/lib/access_control/base.rb:67:
warning: Object#id will be deprecated; use Object#object_id
Account Columns (3.0ms) SHOW FIELDS FROM `accounts`
Account Load (0.4ms) SELECT * FROM `accounts` WHERE
(`accounts`.`id` = '--- :false\n')
CACHE (0.0ms) SELECT * FROM `accounts` WHERE (`accounts`.`id` =
'--- :false\n')

Since I get the loading page instead of the login page (I have to
clear the cookies to get the login page again) I think there is a
problem with the login.
I believe the loading page should not be visible until I successfully
logged in. The above errors also suggest the login was not successful,
because there is no logged in user.
I have no idea what should I do. I did rake db:migrate:reset, clear my
cookies, etc, but no luck.

Thank you

Davide D'Agostino

unread,
Mar 18, 2010, 11:15:39 AM3/18/10
to lipsi...@googlegroups.com
Can you try on a fresh ruby 1.8.7-p72 ?
---
Best Regards,
Davide D'Agostino

Tel. 0331-386985
Mobile. 349-7079458
Fax. 0331-812061

http://www.lipsiasoft.com

AL

unread,
Mar 18, 2010, 11:48:34 AM3/18/10
to Lipsiadmin
I tried and I have exactly the same result.

On Mar 18, 4:15 pm, Davide D'Agostino <d.dagost...@lipsiasoft.com>
wrote:

Davide D'Agostino

unread,
Mar 18, 2010, 11:53:29 AM3/18/10
to lipsi...@googlegroups.com
It's super strange, the problems seems to be routing related:

"No route matches "/backend/base" with {:method=>:get}"

do you have: map.backend '/backend/base', :controller => 'backend/base', :action => 'index' in routes?

You are using rails 2.3.5 ?

---
Best Regards,
Davide D'Agostino

Tel. 0331-386985
Mobile. 349-7079458
Fax. 0331-812061

http://www.lipsiasoft.com

AL

unread,
Mar 18, 2010, 12:20:31 PM3/18/10
to Lipsiadmin
On Mar 18, 4:53 pm, Davide D'Agostino <d.dagost...@lipsiasoft.com>
wrote:

> It's super strange, the problems seems to be routing related:
>
> "No route matches "/backend/base" with {:method=>:get}"
>
> do you have:   map.backend '/backend/base',                :controller => 'backend/base',        :action => 'index' in routes?
>
No, I only have:
map.backend '/backend', :controller =>

'backend/base', :action => 'index'

I have not touched the routes, I did only script/generate backend.
I tried to change my route to /backend/base and I also uncommented my
hack in account_access.rb but nothing changed. I have the same
results, just the route changed.

> You are using rails 2.3.5 ?
>

Yes.

AL

unread,
Mar 18, 2010, 1:06:17 PM3/18/10
to Lipsiadmin
Update: Meanwhile I tried to install lipsiadmin as a plugin into a
fresh rails app. It works.
Now, I "only" have to found out why it does not work in my app...

AL

unread,
Mar 18, 2010, 1:23:51 PM3/18/10
to Lipsiadmin
Btw is there any way to use the app's auth system (and related models)
instead of the builtin system, models?
I already have User model and if I install lipsiadmin I will have an
Account model too.
I started to suspect the auth system in my app conflicts with
lipsiadmin's auth system.
Reply all
Reply to author
Forward
0 new messages