Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 46360 invoked from network); 7 Oct 2005 02:07:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Oct 2005 02:07:06 -0000 Received: (qmail 39652 invoked by uid 500); 7 Oct 2005 02:07:04 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 39628 invoked by uid 500); 7 Oct 2005 02:07:03 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 39617 invoked by uid 99); 7 Oct 2005 02:07:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Oct 2005 19:07:03 -0700 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [66.163.169.225] (HELO smtp105.mail.sc5.yahoo.com) (66.163.169.225) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 06 Oct 2005 19:07:06 -0700 Received: (qmail 2408 invoked from network); 7 Oct 2005 02:06:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer; b=RI7zQi2dX6ZDzrPpxbKP2fBJ98p8gzFY42L4W9gif79FOxwshrI+3DXaZzknk4xve2UqofkdsE/kGolaTKtQ/qui0kSsQq+xE9doHgsjSZRl6y2vO8GBJJwAeE/6wVaI8+1pvUJ2ZkK9jpO66TiIeYQH/G6jLimNW5flYXUwJ40= ; Received: from unknown (HELO ?172.20.100.222?) (david?jencks@71.16.104.146 with plain) by smtp105.mail.sc5.yahoo.com with SMTP; 7 Oct 2005 02:06:38 -0000 Mime-Version: 1.0 (Apple Message framework v622) In-Reply-To: References: <4343A052.000004.13771@tide.yandex.ru> <434495F4.000001.04878@tide.yandex.ru> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <50bd899dd526c63a0fa500f2d502ea65@yahoo.com> Content-Transfer-Encoding: 7bit From: David Jencks Subject: Re: Custom login module Date: Thu, 6 Oct 2005 22:06:35 -0400 To: user@geronimo.apache.org X-Mailer: Apple Mail (2.622) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Oct 5, 2005, at 11:25 PM, Scott Anderson wrote: > On 10/5/05, Ivan S. Dubrov wrote: >> Hello, >> >>> My hack was a little cleaner. I was adding the jar containing my >>> custom login modules as a dependancy to first j2ee-server-plan.xml >>> but >>> since the j2ee-security-plan.xml was established I have had to move >>> the dependancy for my security jar up to the parent configuration of >>> both the server and security plans; naming-server-plan.xml. >> >> I've tried to redeploy these plans, but no luck. Did you redeployed >> them or built server from sources with modified plans? >> >> Anyway, I think this is bug, since I've done things exactly (I think >> so) as they described here: >> http://chariotsolutions.com/geronimo/geronimo-html-one- >> page.html#security-custom >> > > I was following the same script and also could not get it to work as > advertised. As far as I know to deploy updated geronimo plans you do > need the geronimo source. I have found that you are required to > re-build the assembly module to get any changes to the plans in the > modules/assembly/src/plan directory deployed. > I find Aaron's book a little unclear as to whether you are intended to amend the standard geronimo plans or include your login module/security realm configuration in a separate plan, so I'm not quite as clear that the procedure he describes doesn't work. I was worried that this situation with login module classloaders would occur, and sure enough it has: the inability to use custom login modules in other configurations is definitely a bug. I've entered a bug http://issues.apache.org/jira/browse/GERONIMO-1044 to make sure we remember to fix this. It is actually possible to rebuild the plans without the geronimo source. The original plans are supplied in doc/plans and you can edit them and redeploy. thanks david jencks