Return-Path: Delivered-To: apmail-geronimo-scm-archive@www.apache.org Received: (qmail 21902 invoked from network); 12 Oct 2007 13:45:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Oct 2007 13:45:41 -0000 Received: (qmail 82349 invoked by uid 500); 12 Oct 2007 13:45:29 -0000 Delivered-To: apmail-geronimo-scm-archive@geronimo.apache.org Received: (qmail 82339 invoked by uid 500); 12 Oct 2007 13:45:29 -0000 Mailing-List: contact scm-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 scm@geronimo.apache.org Received: (qmail 82328 invoked by uid 99); 12 Oct 2007 13:45:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Oct 2007 06:45:28 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Oct 2007 13:45:40 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 3F2431A9832; Fri, 12 Oct 2007 06:45:20 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r584163 - /geronimo/server/branches/2.0.2/RELEASE_NOTES-2.0.2.txt Date: Fri, 12 Oct 2007 13:45:19 -0000 To: scm@geronimo.apache.org From: kevan@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20071012134520.3F2431A9832@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: kevan Date: Fri Oct 12 06:45:18 2007 New Revision: 584163 URL: http://svn.apache.org/viewvc?rev=584163&view=rev Log: Update MEJB group information Modified: geronimo/server/branches/2.0.2/RELEASE_NOTES-2.0.2.txt Modified: geronimo/server/branches/2.0.2/RELEASE_NOTES-2.0.2.txt URL: http://svn.apache.org/viewvc/geronimo/server/branches/2.0.2/RELEASE_NOTES-2.0.2.txt?rev=584163&r1=584162&r2=584163&view=diff ============================================================================== --- geronimo/server/branches/2.0.2/RELEASE_NOTES-2.0.2.txt (original) +++ geronimo/server/branches/2.0.2/RELEASE_NOTES-2.0.2.txt Fri Oct 12 06:45:18 2007 @@ -28,8 +28,11 @@ Significant Changes in the 2.0.2 Release ---------------------------------------- +- Updated CA (Certification Authority) Helper on the Geronimo Administration Console + * Certificate requests and downloads are now supported using Internet Explorer + - MEJB security issue fixed - * Access to the Maintenance EJB (MEJB) is now controlled by the mejb-read (read access) + * Access to the Maintenance EJB (MEJB) is now controlled by the admin (read access) and mejb-admin (read/write access) groups. - Changes in the default JNDI names for EJB's @@ -37,9 +40,6 @@ on the default JNDI names generated by Geronimo 2.0.1 will not work with Geronimo 2.0.2 For information on the new format, see http://cwiki.apache.org/GMOxDEV/client-jndi-names.html -- Updated CA (Certification Authority) Helper on the Geronimo Administration Console - * Certificate requests and downloads are now supported using Internet Explorer - - Multiple bug fixes * A number of issues are resolved by Geronimo 2.0.2. A summary of issues is provided below. @@ -146,11 +146,6 @@ To prevent potential security exposures, we strongly recommend you update the default user names and passwords on your system. -To enable MEJB access, you will need to configure either an mejb-user or -mejb-admin group. To enable read/write MEJB access to the 'system' user, -add the following to /var/security/groups.properties file: - -mejb-admin=system Deploying Applications ---------------------- @@ -196,9 +191,16 @@ changed are already included in the supplied config.xml file, while others may need to be added manually. +To enable MEJB write access, you will need to configure either an mejb-admin +group. For example, to enable read/write MEJB access to the 'system' user, +add the following to /var/security/groups.properties file: + +mejb-admin=system + Known Issues and Limitations ---------------------------- + Spring jars packaged within the lib directory of an EAR file will not be accessible to web applications packaged within the same EAR file. To workaround this issue you must either override Spring class filtering which is automatically configured