Simply, don't use merb-auth-password-slice. Refer the READMEs inside merb-auth-core and -more directories to implement your own stuff. -auth-more and -auth-password-slice are optional.
- highandwild On Tue, Oct 28, 2008 at 9:13 PM, Jon Hancock <[EMAIL PROTECTED]> wrote: > > I have studied the latest 0.9.10 merb-auth, merb-auth-core, merb-auth- > more, and merb-auth-password-slice. > > I'm still confused as to how to get this to work for me. > > The docs tell me that this new auth structure only authenticates > sessions and has not preference to how I write the auth logic. > However, the auth-password-slice goes forward and adds salt and > crypt_password fields to my User model. Its even so presumptuous as > to see that I have datamapper running and use the dm form of injecting > properties. I absolutely do not want this kind of magic going on in > my app. > > So the first question is: > > 1 - How do I get the slice to keep its hands off my User model? What > I want is a simple list of methods that my User should implement and I > will implement those. The docs indicate that this is what I should be > able to do, but the real world default behavior is different. > > 2 - How do I tell this auth framework which erb file I want to use for > my login form? The slice has its own forms. I do not want to pass > lots of config directives to get the form to look almost correct. I > want to completely replace the form and I want to do so without > monkeypatching the slice. How do I do this? > > thanks, Jon > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
