esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hirsch, Richard" <>
Subject RE: MetaMegaProtoUser Usage in ESME
Date Sat, 04 Apr 2009 09:44:32 GMT
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?


From: David Pollak []
Sent: Fri 03.04.2009 18:07
Subject: Re: MetaMegaProtoUser Usage in ESME

On Thu, Apr 2, 2009 at 1:38 PM, Hirsch, Richard

> I've been exploring lift and have found the MetaMegaProtoUser object (
> 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 <> 
Beginning Scala
Follow me:
Git some:

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message