On 10/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > 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
I should have reported this early. This should read "Updated CA (Certification Authority) Helper application". CA Helper application is not part of the Admin Console. Not a big thing though, but, do consider this change if there is an need to spin another RC. + > - 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 <geronimo_home>/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 <geronimo_home>/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 > > >
