Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 66321 invoked from network); 13 Nov 2006 12:05:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Nov 2006 12:05:10 -0000 Received: (qmail 97162 invoked by uid 500); 13 Nov 2006 12:05:10 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 97089 invoked by uid 500); 13 Nov 2006 12:05:10 -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 97052 invoked by uid 99); 13 Nov 2006 12:05:09 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Nov 2006 04:05:09 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Nov 2006 04:04:58 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 644CD714310 for ; Mon, 13 Nov 2006 04:04:38 -0800 (PST) Message-ID: <32117237.1163419478407.JavaMail.jira@brutus> Date: Mon, 13 Nov 2006 04:04:38 -0800 (PST) From: "Vamsavardhana Reddy (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Created: (GERONIMO-2560) Realm added using SecurityRealm portlet does not work MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Realm added using SecurityRealm portlet does not work ----------------------------------------------------- Key: GERONIMO-2560 URL: http://issues.apache.org/jira/browse/GERONIMO-2560 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console, security Affects Versions: 1.2 Reporter: Vamsavardhana Reddy Fix For: 1.2 A new security realm added using SecurityRealm portlet does not get listed in the portlet. There are no deployment errors. Also, if an application is configured to authenticate against this realm, login is failing since the realm could not be found. The deployment plan for security realms generated in the console seems to use a "service" tag in place of "gbean" tag. If the service tag is changed to gbean tag, the realm is getting listed in the SecurityRealm portlet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira