Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 12205 invoked from network); 2 Nov 2004 01:25:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Nov 2004 01:25:45 -0000 Received: (qmail 62437 invoked by uid 500); 2 Nov 2004 01:25:35 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 62398 invoked by uid 500); 2 Nov 2004 01:25:35 -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 Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 62369 invoked by uid 99); 2 Nov 2004 01:25:34 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 01 Nov 2004 17:25:33 -0800 Received: (qmail 24892 invoked from network); 2 Nov 2004 01:25:32 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 2 Nov 2004 01:25:32 -0000 Message-ID: <1748509652.1099358732010.JavaMail.apache@nagoya> Date: Mon, 1 Nov 2004 17:25:32 -0800 (PST) From: "Aaron Mulder (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Created: (GERONIMO-416) Client Container should handle login Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Client Container should handle login ------------------------------------ Key: GERONIMO-416 URL: http://nagoya.apache.org/jira/browse/GERONIMO-416 Project: Apache Geronimo Type: Improvement Versions: 1.0-M2 Reporter: Aaron Mulder It would be nice if the application client container would use the Callback Handlers provided in application-client.xml to perform a login. That way, an application client does not need server-specific code to log in, it just provides callback handlers and lets them get invoked magically by the client container to collect a username and password, or whatever. There's some debate over when this should happen. We could do it immediately at client container startup, or on demand when the user first attempts to access a secure resource. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira