Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 37575 invoked from network); 4 Apr 2009 09:45:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Apr 2009 09:45:08 -0000 Received: (qmail 62830 invoked by uid 500); 4 Apr 2009 09:45:08 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 62785 invoked by uid 500); 4 Apr 2009 09:45:08 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 62775 invoked by uid 99); 4 Apr 2009 09:45:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2009 09:45:08 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [194.138.12.131] (HELO mxs1.siemens.at) (194.138.12.131) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2009 09:44:59 +0000 Received: from vies1k7x.sie.siemens.at ([158.226.129.83]) by mxs1.siemens.at with ESMTP id n349iZjh004839 for ; Sat, 4 Apr 2009 11:44:35 +0200 Received: from nets139a.ww300.siemens.net ([192.168.217.3]) by vies1k7x.sie.siemens.at (8.12.11.20060308/8.12.1) with ESMTP id n349iZG2029114 for ; Sat, 4 Apr 2009 11:44:35 +0200 Received: from nets13ja.ww300.siemens.net ([158.226.250.79]) by nets139a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 4 Apr 2009 11:44:34 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C9B509.F4A1F247" Subject: RE: MetaMegaProtoUser Usage in ESME Date: Sat, 4 Apr 2009 11:44:32 +0200 Message-ID: <30DB6ACF50A0A3439F39EFEB1C52E166078F23E6@nets13ja.ww300.siemens.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: <30DB6ACF50A0A3439F39EFEB1C52E166078F23E6@nets13ja.ww300.siemens.net> Thread-Topic: MetaMegaProtoUser Usage in ESME Thread-Index: Acm0dnAb6dx3zSd8TFGDGIlrTTBorQAksHuL References: <9d8b82ea0904011559v491eee0ah83612ed2929a7b6e@mail.gmail.com><0016799C-60A9-467B-86DD-08D59001661E@gmail.com><30DB6ACF50A0A3439F39EFEB1C52E166078F23E0@nets13ja.ww300.siemens.net> From: "Hirsch, Richard" To: X-OriginalArrivalTime: 04 Apr 2009 09:44:34.0706 (UTC) FILETIME=[F6396720:01C9B509] X-purgate: clean X-purgate: This mail is considered clean X-purgate-type: clean X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net X-purgate-ID: 149917::090404114435-0B9D8BA0-5A27F6EA/0-0/0-15 X-purgate-size: 8751/0 X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C9B509.F4A1F247 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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.=20 =20 Is it possible to change the UI for the MetaMegaProtoUser functionality? =20 D.=20 ________________________________ From: David Pollak [mailto:feeder.of.the.bears@gmail.com] Sent: Fri 03.04.2009 18:07 To: esme-dev@incubator.apache.org Subject: Re: MetaMegaProtoUser Usage in ESME On Thu, Apr 2, 2009 at 1:38 PM, Hirsch, Richard wrote: > I've been exploring lift and have found the MetaMegaProtoUser object ( > = http://scala-tools.org/scaladocs/liftweb/1.0/net/liftweb/mapper/MetaMegaP= rotoUser.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 = =20 Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Git some: http://github.com/dpp ------_=_NextPart_001_01C9B509.F4A1F247--