Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 44780 invoked from network); 26 Oct 2006 17:31:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Oct 2006 17:31:02 -0000 Received: (qmail 10871 invoked by uid 500); 26 Oct 2006 17:31:09 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 10822 invoked by uid 500); 26 Oct 2006 17:31:09 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 10811 invoked by uid 99); 26 Oct 2006 17:31:09 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Oct 2006 10:31:09 -0700 X-ASF-Spam-Status: No, hits=2.8 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [68.142.206.237] (HELO smtp104.plus.mail.mud.yahoo.com) (68.142.206.237) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 26 Oct 2006 10:30:54 -0700 Received: (qmail 26496 invoked from network); 26 Oct 2006 17:30:33 -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=U2V2ba3oxjwux1f8qDFGDCI2sUdVUwaSPjp08PlUBauyx4NKIUCfNfvvSAbgHB/pooSejgX6pqpXCRcZ1lnaAAcywVXiD85214FEECZ+SWNYP+f1g03LvrF5+0qJlWfJOAfJtKFDae6YbHFJx2Iarc5dLurpyS7RBJ4cw2K7008= ; Received: from unknown (HELO ?10.11.55.8?) (david?jencks@63.105.20.225 with plain) by smtp104.plus.mail.mud.yahoo.com with SMTP; 26 Oct 2006 17:30:33 -0000 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <444AB1B3.5050101@cox.net> References: <74e15baa0604211254u5c69f063l95bff7b3c8936cd3@mail.gmail.com> <444A6AF2.2050801@toolazydogs.com> <444AAE10.3090003@cox.net> <444AB1B3.5050101@cox.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: David Jencks Subject: Re: where's JACC provider implementation? Date: Thu, 26 Oct 2006 10:30:35 -0700 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org My apologies for the extremely late response, this appears to have been sent when my mail wasn't really working. On the other hand in April JACC wasn't pluggable and it is now :-) (almost completely, I hope) The default Geronimo JACC provider is in org.apache.geronimo.security.jacc in the GeronimoPolicyConfigurationFactory and PolicyConfigurationGeneric classes. I suspect we should move these into a different package to make it clear they are the JACC provider rather than the infrastructure geronimo provides. If you want to configure the JACC implementation with non-spec information from geronimo plans you will also need to write a builder similar to the o.a.g.security.deployment.GeronimoSecurityBuilderImpl that reads info from its own xml namespace. If the non-spec information is intended to come from a different source (not geronimo plans) you won't need one of these builders. I recently set up a skeleton example of how a JACC provider could be plugged in, http://www.nabble.com/TripleSec-Geronimo-integration- tf2444664.html#a6815690 It would be great to get another working JACC implementation installed, so if you have any questions how to proceed please ask! thanks david jencks On Apr 22, 2006, at 3:44 PM, argyn wrote: > i started looking into code in org.apache.geronimo.security.jacc > package-summary.html> package. basically, i want to figure out how > to plug the custom JACC provider into Geronimo, so i need to look > at the existing ones. where's your default jacc provider? > > thanks, > argyn >