Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 55289 invoked from network); 6 Jun 2002 00:58:57 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 6 Jun 2002 00:58:57 -0000 Received: (qmail 22597 invoked by uid 97); 6 Jun 2002 00:59:00 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 22466 invoked by uid 97); 6 Jun 2002 00:59:00 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 22335 invoked by uid 98); 6 Jun 2002 00:58:59 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Subject: Mulitple components of same ROLE From: Richard Wallace To: avalon-phoenix-dev@jakarta.apache.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 05 Jun 2002 17:58:55 -0700 Message-Id: <1023325135.13386.34.camel@rw-linux> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hey guys, I've been working with Larry on a AAA (Authentication/Authorization/Auditing) framework for cornerstone. One of the things that we're discussing is if we should have support for multiple Realms similar to the way PAM and JAAS have multiple LoginModules. I'm thinking that it would be similar in function to the way JAAS does it, but alleviates the need for relying on the JAAS API and creating a JAASRealm that would have to be used to get this feature. I have two questions about this, I guess: 1) Does this sound like a feature people would be interested in? If there isn't a lot of need for it we'll put it on the back burner and maybe write an implementation later that will support it. 2) We're deciding that (at least within phoenix) Realms will be configured and provided to the Authenticator as blocks. So, if we decide to support multiple realms how do we provide multiple components that implement the same role (in this case Realm) to a Serviceable component? Or would that not be the right interface to implement? What, other than Serviceable, should it become to accomplish this? Thanks. -- Richard Wallace AIM, Inc. (www.a--i--m.com) Information Systems Consultants "Providing New Technology, the Old-Fashioned Way" -- To unsubscribe, e-mail: For additional commands, e-mail: