I think MetaMegaProtoUser is a little too mega for my tastes...

I'm going to make an attempt at diving into the code this afternoon and see
what I can come up with.  But I'd like to see the user be a little less mega
and a little more pluggable.  So my inkling is to remove the dependency on
MetaMegaProtoUser, not increase it.  We'll see where that goes...

On Sat, Apr 4, 2009 at 5:44 AM, Hirsch, Richard
<[email protected]>wrote:

> Any chance that someone can make this change?  The MetaMegaProtoUser has
> functionality (changing password, registering, etc) that our users want. To
> be honest, if the combination of OpenID and MetaMegaProtoUser  leads to
> conflicts I'd rather have the MetaMegaProtoUser.
>
> Is it possible to change the UI for the MetaMegaProtoUser functionality?
>
> D.
>
> ________________________________
>
> From: David Pollak [mailto:[email protected]]
> Sent: Fri 03.04.2009 18:07
> To: [email protected]
> Subject: Re: MetaMegaProtoUser Usage in ESME
>
>
>
> On Thu, Apr 2, 2009 at 1:38 PM, Hirsch, Richard
> <[email protected]>wrote:
>
> > I've been exploring lift and have found the MetaMegaProtoUser object (
> >
> http://scala-tools.org/scaladocs/liftweb/1.0/net/liftweb/mapper/MetaMegaProtoUser.html
> )
> > which actually has tons of functionality out-of-the-box regarding user
> > registration.
> >
> > Could we use this functionality? Either in addition to OpenID or instead
> of
> > OpenID?
>
>
> The OpenID stuff sits on top of MetaMegaProtoUser (what moron named this
> stuff?  Oh... right... it was me.)
>
> What we need to do is abstract away the authentication method into another
> table from the user and optionally allow a user to have multiple
> authentication mechanisms (NTLM, Kerberos, OpenID, username/password).
>
> My backlog sucks.
>
>
> >
> >
> > D.
> >
> >
>
>
> --
> Lift, the simply functional web framework http://liftweb.net <
> http://liftweb.net/>
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Git some: http://github.com/dpp
>
>
>


-- 
http://erikengbrecht.blogspot.com/

Reply via email to