Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 40201 invoked from network); 12 Aug 2010 10:52:55 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 Aug 2010 10:52:55 -0000 Received: (qmail 49755 invoked by uid 500); 12 Aug 2010 10:52:55 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 49693 invoked by uid 500); 12 Aug 2010 10:52:53 -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 49685 invoked by uid 99); 12 Aug 2010 10:52:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Aug 2010 10:52:52 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of in.imtiaz@gmail.com designates 74.125.83.47 as permitted sender) Received: from [74.125.83.47] (HELO mail-gw0-f47.google.com) (74.125.83.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Aug 2010 10:52:45 +0000 Received: by gwb15 with SMTP id 15so369385gwb.6 for ; Thu, 12 Aug 2010 03:52:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:references :subject:date:mime-version:content-type:content-transfer-encoding :x-priority:x-msmail-priority:x-mailer:x-mimeole; bh=y+cKJAnqLXJBskeWQSRwKEe2JUQFlwaqmhSDAEtoAP8=; b=NqorgMG/PiQFjiNgd66zPTGWDi97RprIh7YD1Y2a3C2k6vzRk3JDANrYxy5RS27YuZ 3GOBkU8y4c04cSC3H53sNr1S7oX1uGaqSoj02Pyy3tpMvCYt9+XTiIgjnfm1k2QQ9x03 IWb+8stO4Z1wHd2OotpA5U+WObCxCAtXKReIQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:references:subject:date:mime-version :content-type:content-transfer-encoding:x-priority:x-msmail-priority :x-mailer:x-mimeole; b=B5E/ck2oFm+0YMiqsiMsjb+t3QwUy/5rX4vmYGWUpCH8rECILZ4ZVMfmTw8BwU+JjU S2zhWw6WyME5ZuazzLapkiWuZIZb6sV0SNNuWL+Be/QrVCyX+lOU5bEsIKAp+DMVbIKw NG8/jxTA0kGJfz2Ar8IU0WwUgKmsxBmJp3wbM= Received: by 10.100.30.18 with SMTP id d18mr18143150and.239.1281610344137; Thu, 12 Aug 2010 03:52:24 -0700 (PDT) Received: from imtiaz20100131 ([122.167.19.243]) by mx.google.com with ESMTPS id p12sm2111017ane.34.2010.08.12.03.52.21 (version=SSLv3 cipher=RC4-MD5); Thu, 12 Aug 2010 03:52:23 -0700 (PDT) Message-ID: <7892404B34994875B70A170B11A24656@imtiaz20100131> From: "Imtiaz Ahmed H E" To: References: <12A3FD81664441BEBA9942B515AA1E03@imtiaz20100131> Subject: Fix for ESME-108 attached to Jira. Date: Thu, 12 Aug 2010 16:22:12 +0530 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 X-Virus-Checked: Checked by ClamAV on apache.org This fix , attached patch EsmeJira108FixPatch.diff, fixes it following the example in http://demo.liftweb.net/rhodeisland;jsessionid=ojmsqzkop0i. Let me know if you need any changes, cosmetic or otherwise... Imtiaz ----- Original Message ----- From: "Richard Hirsch" To: Sent: Sunday, August 08, 2010 10:20 PM Subject: Re: ESME-214... Container based authentication is the idea that the container (jetty, tomcat, etc.) is used to authenticate the user rather than using the ESME internal (Open-ID, username-password) methods. For example, if container authentication would be active then the user can sign on via an external corporate single sign on mechanism and then ESME would take the information from this system and use it as the user id. This may be associated with the use of a corporate LDAP. You might want to take a look at Lift's LDAP support to get an initial impression of what is necessary. Until I get back and do a full spec in JIRA for container-based authentication, ESME 108 might be easier to work on On Sat, Aug 7, 2010 at 1:13 AM, Imtiaz Ahmed H E wrote: > Vassil, > > I have been tutoring myself just a bit on stuff related to ESME-214, > container-based authentication, and would you be in a position to tell me > *exactly* what needs to be done to make this 'resolved/implemented'. I'll > go ahead and do that and submit a patch to the Jira ticket. > > Dick seems to be the originator, and Ethan appears incommunicado for the > past week ! > > Imtiaz > > > ----- Original Message ----- From: "Richard Hirsch" > > To: > Sent: Friday, July 16, 2010 4:10 PM > Subject: Release planning > > >> I've been working on the JIRA items and we have 10 items left for this >> release. >> >> The following items are linked to IE 7: >> * ESME-207 >> * ESME-239 >> * ESME-208 >> >> Some of these items are CSS-related (for example, 207) but the other >> ones are javascript / jquery related. >> >> I think the two main issues are: >> >> * ESME-205 Search is broken (This only happens when you use a JDBC >> based compass indexes - first noticed on Stax but it also is present >> locally) >> * ESME-212 Messages from pools aren't hidden >> >> I'm going to be gone the next four weeks on vacation, so either >> someone else can coordinate the release or we wait until I return to >> continue with our release preparations. >> >> If anyone wants to work on other items until the release, here are >> other items that I consider important: >> >> * ESME-108 - View my pools" functionality >> * ESME-170 Pubsubhubbub support for Atom & RSS actions# >> * ESME-214 Add container-based authentication >> * ESME-213 Twitter API is out-of-date and API calls don't always >> return the correct info >> >> -- other api2 related changes - see the ToDos at the bottom of the >> API2.scala page . >> >> D. > >