Maybe a stupid question here, but could you not make AdminUser a subclass of User and turn off the authlogic on User methods? I guess what I'm asking here is are there certain design requirements in your project which dictate that the AdminUser class *must* be separated from the base User class?
It seems that if the AdminUser needs to be separate — and you need to user authlogic — the logical choice would be to fork the gem and make your modifications to that copy instead of monkeying around in the official gem. It may also be easier to just add access control to the existing User class which allows certain users to be Admins. Just trying to wrap my head around this. :) On Nov 26, 6:28 am, athem <[email protected]> wrote: > Hello, > > I want to implement authentication using the authlogic gem in an > application that already implements a User model that I cannot > modify. The authlogic authentication would be for something like a > new AdminUser model, completely separate from the existing User model. > > Since authlogic is installed as a gem on the server (and used by other > applications), the gem code itself cannot be modified. > > Any tips for where to begin/how to approach this? > > thanks. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
