Author: jaredmorgs
Date: 2011-12-07 23:49:17 -0500 (Wed, 07 Dec 2011)
New Revision: 8210
Modified:
epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml
epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml
epp/docs/branches/5.2/Release_Notes/en-US/feature_requests.xml
epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml
epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml
epp/docs/branches/5.2/Release_Notes/publican.cfg
Log:
Rebrewed book with CVE notes added and Support links section updated
Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml 2011-12-08 03:29:08
UTC (rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml 2011-12-08 04:49:17
UTC (rev 8210)
@@ -188,6 +188,33 @@
<para>For detailed information about component versions included in this
release, refer to <xref
linkend="Release_Notes-Component_Features"/></para>
</note>
</chapter>
+ <chapter id="Release_Notes-Documentation">
+ <title>Documentation</title>
+ <para>
+ An <citetitle>Installation Guide</citetitle> and a
<citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are
available at <ulink
url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf...
type="http"/>. JBoss Enterprise Portal Platform specific documentation is
also available from this location.
+ </para>
+ </chapter>
+ <chapter
id="Release_Notes-_Product_Support_and_License_Website_Links_">
+ <title> Product Support Links </title>
+ <formalpara
id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes">
+ <title>Product Update and Support Processes</title>
+ <para>
+ <ulink
url="https://access.redhat.com/support/policy/updates/jboss_notes/&q...
+ </para>
+ </formalpara>
+ <formalpara
id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_">
+ <title> Developer Support Scope of Coverage, and Service Level
Agreement</title>
+ <para><ulink
url="https://access.redhat.com/support/offerings/developer/">...
+
+ </para>
+ </formalpara>
+ <formalpara
id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_">
+ <title>Certified and Compatible Configurations</title>
+ <para>
+ <ulink
url="http://www.jboss.com/products/platforms/portals/testedconfigura...
+ </para>
+ </formalpara>
+ </chapter>
<chapter>
<title>New Features</title>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="feature_requests.xml" encoding="XML"/>
@@ -218,56 +245,5 @@
<para>
Stuff about migration from 5.1.0 to 5.1.1.
</para>
- </chapter>--> <chapter
id="Release_Notes-Documentation">
- <title>Documentation</title>
- <para>
- An <citetitle>Installation Guide</citetitle> and a
<citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are
available at <ulink
url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf...
type="http"/>. JBoss Enterprise Portal Platform specific documentation is
also available from this location.
- </para>
- </chapter>
- <chapter
id="Release_Notes-_Product_Support_and_License_Website_Links_">
- <title> Product Support and License Website Links </title>
- <formalpara
id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes">
- <title>Support Processes</title>
- <para>
- <ulink
url="http://www.redhat.com/support/process/">http://www.redh...
- </para>
- </formalpara>
- <formalpara
id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Scope_of_Coverage_">
- <title> Production Support Scope of Coverage </title>
- <para>
- <ulink
url="http://www.redhat.com/support/policy/soc/production">ht...
- </para>
- </formalpara>
- <formalpara
id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Production_Support_Service_Level_Agreement_">
- <title> Production Support Service Level Agreement </title>
- <para>
- <ulink
url="http://www.redhat.com/support/policy/sla/production/">h...
- </para>
- </formalpara>
- <formalpara
id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Scope_of_Coverage_">
- <title> Developer Support Scope of Coverage </title>
- <para>
- <ulink
url="http://www.redhat.com/support/policy/soc/developer/">ht...
- </para>
- </formalpara>
- <formalpara
id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Developer_Support_Service_Level_Agreement_">
- <title> Developer Support Service Level Agreement </title>
- <para>
- <ulink
url="http://www.redhat.com/support/policy/sla/developer/">ht...
- </para>
- </formalpara>
- <formalpara
id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_Product_Update_and_Support_Policy_by_Product_">
- <title> Product Update and Support Policy by Product </title>
- <para>
- <ulink
url="http://www.redhat.com/security/updates/jboss_notes/">ht...
- </para>
- </formalpara>
- <formalpara
id="form-Release_Notes-_Product_Support_and_License_Website_Links_-_JBoss_End_User_License_Agreement_">
- <title> JBoss End User License Agreement </title>
- <para>
- <ulink
url="http://www.redhat.com/licenses/jboss_eula.html">http://...
- </para>
- </formalpara>
- </chapter>
- <xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="Revision_History.xml"/>
+ </chapter>--> <xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="Revision_History.xml"/>
</book>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-12-08 03:29:08 UTC (rev
8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-12-08 04:49:17 UTC (rev
8210)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.0</edition>
- <pubsnumber>8</pubsnumber>
+ <pubsnumber>10</pubsnumber>
<abstract>
<para>
These release notes contain important information related to JBoss Enterprise
Portal Platform &VZ; that may not be currently available in the Product Manuals. You
should read these Release Notes in their entirety before installing the product.
Modified: epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2011-12-08 03:29:08 UTC
(rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2011-12-08 04:49:17 UTC
(rev 8210)
@@ -8,8 +8,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>5.2.0-8</revnumber>
- <date>Mon Dec 05 2011</date>
+ <revnumber>5.2.0-10</revnumber>
+ <date>Thu Dec 08 2011</date>
<author>
<firstname>Jared</firstname>
<surname>Morgan</surname>
@@ -17,7 +17,7 @@
</author>
<revdescription>
<simplelist>
- <member>Third Draft of Enterprise Portal Platform 5.2.0 Release Notes,
considered to be the final draft before GA.</member>
+ <member>Third Draft respin of Enterprise Portal Platform 5.2.0 Release
Notes, with changes to Product Support Links and some CVE XSS issues. This is considered
to be the final draft before GA.</member>
</simplelist>
</revdescription>
</revision>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/feature_requests.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/feature_requests.xml 2011-12-08 03:29:08 UTC
(rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/feature_requests.xml 2011-12-08 04:49:17 UTC
(rev 8210)
@@ -1,340 +1,502 @@
-<?xml version='1.0' encoding='UTF-8'?>
+<?xml version='1.0'?>
<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
+
+
<variablelist>
-<!--
https://issues.jboss.org/browse/JBEPP-736 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-736">JBEPP-736<...
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-736 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-736">JBEPP-736<...
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
It is possible to switch portal clusters between UDP and TCP communication modes
using a command-line parameter. The -Dgatein.default.jgroups.stack=[tcp | udp] parameter
switches EPP clusters (JCR, IDM, MOPSessionManager, NavigationService, DescriptionService)
between the two protocols. The functionality is implemented using an adapted, and mutually
exclusive implementation of jboss.default.jgroups.stack.
-</para>
- <note>
- <para>This enhancement is based on, but deliberately independent of, the
JBoss Enterprise Application Platform parameter.
"jboss.default.jgroups.stack" which supports more values by default than
Enterprise Portal Platform currently does. The decision to keep the two parameters
separate was for upstream compatibility.
+<note><para>This enhancement is based on, but deliberately independent of,
the JBoss Enterprise Application Platform parameter.
"jboss.default.jgroups.stack" which supports more values by default than
Enterprise Portal Platform currently does. The decision to keep the two parameters
separate was for upstream compatibility.</para></note>
</para>
- </note>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-932 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-932">JBEPP-932<...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-932 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-932">JBEPP-932<...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
URL handler support is available in this release. The WCM component uses this
feature to support locales as part of the URL.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-933 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-933">JBEPP-933<...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-933 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-933">JBEPP-933<...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Performance bottlenecks have been removed when a portal runs with hundreds of
navigation nodes.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-934 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-934">JBEPP-934<...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-934 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-934">JBEPP-934<...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
In previous releases, navigation node translations had to be managed in language
property files. This release allows Navigation nodes to be translated directly through the
administration interface.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-937 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-937">JBEPP-937<...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-937 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-937">JBEPP-937<...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
It is now possible to define a portlet.xml that describes elements such as
filters that need to be applied to all portlets. The file is located in
jboss-as/server/[configuration]/conf/gatein/portlet.xml
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-938 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-938">JBEPP-938<...
- </term>
- <listitem>
- <remark>Assignee is: mwringe</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-938 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-938">JBEPP-938<...
+ <listitem>
+
+ <remark>Assignee is: mwringe</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
This release upgrades Shindig to version 2.0.2. Shindig is used to embed
OpenSocial gadgets. Refer to the Component Versions section for the definitive version
featured in this release.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-939 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-939">JBEPP-939<...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-939 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-939">JBEPP-939<...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Web service security between WSRP producers and consumers is available in this
release. This enhancement allows for encrypted communication and access to authenticated
user content over WSRP.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-940 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-940">JBEPP-940<...
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-940 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-940">JBEPP-940<...
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
This release makes it possible to configure several LDAP servers containing
different users with GateIn. In a ReadOnly scenario, the user is searched in all
configured sources. In a ReadWrite scenario, the user is created only in the first
configured LDAP server, but obtained from all.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1008 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1008">JBEPP-1008&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1008 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1008">JBEPP-1008&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
Application registry categories are now cached for better performance.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1015 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1015">JBEPP-1015&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1015 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1015">JBEPP-1015&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Each site can now have a site description, which can be accessed and used by the
management applications.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1016 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1016">JBEPP-1016&...
- </term>
- <listitem>
- <remark>Assignee is: mwringe</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1016 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1016">JBEPP-1016&...
+ <listitem>
+
+ <remark>Assignee is: mwringe</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Priority for the loading of skin css files can now be specified in
gatein-resources.xml using the css-priority xml element. This allows the css elements to
be loaded in a specific order, which can be useful for overriding existing css elements.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1045 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1045">JBEPP-1045&...
- </term>
- <listitem>
- <remark>Assignee is: claprun</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1045 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1045">JBEPP-1045&...
+ <listitem>
+
+ <remark>Assignee is: claprun</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
WSRP was previously unavailable for portal extensions. The new WSRP component
now properly initializes itself even when started from an extension (as opposed to the
default portal container).
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1077 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1077">JBEPP-1077&...
- </term>
- <listitem>
- <remark>This issue is unassigned!</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1077 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1077">JBEPP-1077&...
+ <listitem>
+
+ <remark>This issue is unassigned!</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The datasource for JCR is now using managed transactions, and required a change
in the datasource descriptor.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1078 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1078">JBEPP-1078&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1078 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1078">JBEPP-1078&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
EPP is now partially available in Czech language.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1088 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1088">JBEPP-1088&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1088 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1088">JBEPP-1088&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
When adding a page to a site, pages are displayed in a drop-down list instead of
a free form text field. This makes adding pages more intuitive.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1098 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1098">JBEPP-1098&...
- </term>
- <listitem>
- <remark>Assignee is: mwringe</remark>
- <remark>JIRA is Closed</remark>
- <para>
- This release of JBoss Enterprise Portal Platform adds a configurable setting to
control whether the 'info bar' which surrounds new portlets is displayed
by default.
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1098 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1098">JBEPP-1098&...
+ <listitem>
+
+ <remark>Assignee is: mwringe</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ This release of JBoss Enterprise Portal Platform adds a configurable setting to
control whether the 'info bar' which surrounds new portlets is displayed by
default.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1099 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1099">JBEPP-1099&...
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1099 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1099">JBEPP-1099&...
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
In this release, the Single Sign On (SSO) component has been enhanced to support
FORM authentication for instances where the user can not get access to SSO authentication
sessions (such as a Kerberos ticket). Users can now authenticate manually with the
portal-specific username and password as a fall-back.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1116 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1116">JBEPP-1116&...
- </term>
- <listitem>
- <remark>Assignee is: claprun</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1116 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1116">JBEPP-1116&...
+ <listitem>
+
+ <remark>Assignee is: claprun</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Configuring a page is no longer restricted to local portlets. It is now possible
to define remote portlets (WSRP) in page descriptors to populate the base data for the
page.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1140 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1140">JBEPP-1140&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1140 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1140">JBEPP-1140&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
In previous releases, the portal did not indicate it had started clearly in the
logs. Changes to core portal code now specifies the portal has started in the logs, and
includes the portal version number for reference.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1149 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1149">JBEPP-1149&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1149 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1149">JBEPP-1149&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
This release contains enhancements to Gadgets, which, like portlets, can now be
integrated on a page definition through XML descriptors.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1158 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1158">JBEPP-1158&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1158 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1158">JBEPP-1158&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The HTML Document Object Module (DOM) has been optimized to achieve better
performance when transmitting markup, and has been simplified for faster rendering on
recent web browsers. Older browsers such as Internet Explorer will still work, however
performance will be degraded.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1169 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1169">JBEPP-1169&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1169 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1169">JBEPP-1169&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The Apache Shindig configuration file has been made more accessible to be
modified more easily. It is now part of
eXoGadgetServer.war/containers/default/container.js
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1197 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1197">JBEPP-1197&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1197 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1197">JBEPP-1197&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
An enhancement to the UserDashboardImpl object now allows dashboard instances to
be reused. Dashboards now require less resources to operate correctly.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1210 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1210">JBEPP-1210&...
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1210 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1210">JBEPP-1210&...
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Cluster data transportation has been optimized to reduce the number of network
connections and threads.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1250 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1250">JBEPP-1250&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
- When defining navigation in an XML descriptor, it is now possible to define the
strategy to apply during startup. It is possible to "conserve",
"insert", "merge" or "rewrite" the
content previously imported.
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1250 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1250">JBEPP-1250&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ When defining navigation in an XML descriptor, it is now possible to define the
strategy to apply during startup. It is possible to "conserve",
"insert", "merge" or "rewrite" the content previously
imported.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1332 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1332">JBEPP-1332&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1332 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1332">JBEPP-1332&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
In this release the default JCR workspace name and system JCR workspace name can
now be configured in the configuration.properties file.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1349 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1349">JBEPP-1349&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1349 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1349">JBEPP-1349&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
There was no way to determine the Enterprise Portal Platform version, based on
what was displayed when starting the portal. An enhancement to UIFooterPortlet.gtmpl has
been implemented, which allows the user to see what portal version is used by
mouse-hovering in the site footer.
</para>
- </listitem>
- </varlistentry>
+
+ </listitem>
+ </varlistentry>
+
</variablelist>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-12-08 03:29:08 UTC
(rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-12-08 04:49:17 UTC
(rev 8210)
@@ -1,35 +1,4 @@
-<?xml version='1.0'?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<variablelist>
-
- <!--
https://issues.jboss.org/browse/JBEPP-1352 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1352">JBEPP-1352&...
- <listitem>
-
- <remark>Assignee is: hfnukal</remark>
-
-
- <remark>JIRA is Closed</remark>
-
-
- <warning>
- <title>Not Public Yet - RHT only</title>
- <para>
- It was found that JBoss Web Services Native did not properly protect
-against recursive entity resolution when processing Document Type
-Definitions (DTD). A remote attacker could exploit this flaw by sending a
-specially-crafted HTTP POST request to a deployed web service, causing
-excessive CPU and memory consumption on the system hosting that service. If
-the attack is repeated to consume all available network sockets, the server
-will become unavailable. (CVE-2011-1483)
- </para>
- </warning>
-
- </listitem>
- </varlistentry>
-
-</variablelist>
+<para>
+There are no known issues in this release.
+</para>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-12-08 03:29:08 UTC
(rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-12-08 04:49:17 UTC
(rev 8210)
@@ -1,432 +1,626 @@
-<?xml version='1.0' encoding='UTF-8'?>
+<?xml version='1.0'?>
<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
+
+
<variablelist>
-<!--
https://issues.jboss.org/browse/JBEPP-348 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-348">JBEPP-348<...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-site Scripting (XSS) vulnerability was discovered in the portlet
description, which allowed Javascript to be specified in the portlet description through
the application registry. The vulnerability has been fixed in this release.
+
+ <!--
https://issues.jboss.org/browse/JBEPP-348 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-348">JBEPP-348<...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-site Scripting (XSS) vulnerability was discovered in the portlet
description, which allowed Javascript to be specified in the portlet description through
the application registry. The vulnerability has been fixed in this release. <ulink
url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo...
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-353 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-353">JBEPP-353<...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-site Scripting (XSS) vulnerability was discovered when adding a
portlet to a category. The vulnerability has been fixed in this release.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-353 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-353">JBEPP-353<...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-site Scripting (XSS) vulnerability was discovered when adding a
portlet to a category. The vulnerability has been fixed in this release. <ulink
url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo...
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-631 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-631">JBEPP-631<...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-631 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-631">JBEPP-631<...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Remote Gadgets were not persisting data in category gadgets with more than five
categories when the user switched between pages. User data entered in one screen was being
lost when the user switched between pages. The fix implements changes to UIForm.js and
UIFormCheckBoxInput.java which handles selected values reliably when the user switches
between screens.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-699 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-699">JBEPP-699<...
- </term>
- <listitem>
- <remark>This issue is unassigned!</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-699 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-699">JBEPP-699<...
+ <listitem>
+
+ <remark>This issue is unassigned!</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
A bug in UIUserLanguageSelector caused a problem with dynamically updating the
locale when a user selected a different language. The language state had to be saved using
the Apply button. The fix introduces changes to locale handling in the affected module
which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-715 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-715">JBEPP-715<...
- </term>
- <listitem>
- <remark>This issue is unassigned!</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-715 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-715">JBEPP-715<...
+ <listitem>
+
+ <remark>This issue is unassigned!</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The page URL conventions in previous versions of JBoss Enterprise Portal
Platform did not allow for Portal pages to have the same name. In these instances, pages
with identical names were allocated the same URL, with only one page available through it.
A change to the way JBoss Enterprise Portal Platform constructs page URLs resolves this
issue.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-763 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-763">JBEPP-763<...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-763 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-763">JBEPP-763<...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The platform ships with a resource compressor (CSS and Javascript). Some
javascript files were incorrectly compressed and would break unless the developer mode was
enabled. Enabling the developer mode introduced performance side-effects. The Javascript
compression engine has been replaced, and can be turned off if required, which fixes the
issue.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-900 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-900">JBEPP-900<...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-900 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-900">JBEPP-900<...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
A bug in the Logo Portlet caused the processAction methods to be called once
when the first, valid, processAction method was called to submit the value, and again when
the page was rendered. This caused null values to be passed on the second submit. A fix to
UILogoPortlet.gtmpl removes the second processAction call issue, which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-901 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-901">JBEPP-901<...
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- When a "root" user (advanced administrative rights) logs
onto the portal, part of the logon process calls a query that fetches all the groups from
the database. This query was not optimized to handle databases containing very large
numbers of groups. When testing with a large group database, the login process took an
unacceptable amount of time. The fix implements performance improvements to the query, and
provides enhanced caching for large group records.
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-901 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-901">JBEPP-901<...
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ When a "root" user (advanced administrative rights) logs onto the
portal, part of the logon process calls a query that fetches all the groups from the
database. This query was not optimized to handle databases containing very large numbers
of groups. When testing with a large group database, the login process took an
unacceptable amount of time. The fix implements performance improvements to the query, and
provides enhanced caching for large group records.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-903 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-903">JBEPP-903<...
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-903 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-903">JBEPP-903<...
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
An issue was identified when the OrganizationManagementPortlet displayed many
users from the IDM DB. This caused performance issues, specifically impacting load times
for the portlet. The fix implements performance optimizations for specific database
queries related to the process. Load time performance is improved for the portlet.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-908 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-908">JBEPP-908<...
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-908 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-908">JBEPP-908<...
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
A performance issue in a database query that checked for duplicate emails at
user registration caused unacceptable wait times. The larger the user count was in the
database, the more pronounced the issue. The fix implements performance optimization in
the database query. User registration wait time is improved for portal instances with very
large user databases.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-927 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-927">JBEPP-927<...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-927 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-927">JBEPP-927<...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
It is not possible to save notes in the TODO gadget when the gadget is placed
anywhere except a dashboard. This behavior is expected. A workaround to this issue has
been implemented in this version, which allows notes to be entered into this gadget only.
Other gadgets still have this issue.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-950 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-950">JBEPP-950<...
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-950 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-950">JBEPP-950<...
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
An inefficiency in MOPSessionManager cache was causing unacceptable wait
times when an user accessed the portal for the first time, when the portal was idle for an
extended period, or when accessing pages that had not been previously cached. The fix
implements performance improvements for cases where a portal instance has many pages and
navigation nodes, improving overall response time.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-951 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-951">JBEPP-951<...
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-951 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-951">JBEPP-951<...
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
Performance issues were discovered in the portal when editing a navigation,
or portal page that contained many sub-pages. In some cases, the save action was taking
longer than one minute to complete. The fix implements changes to the queries used to
retrieve navigation, or portal pages after saving, which improves load times
significantly.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-983 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-983">JBEPP-983<...
- </term>
- <listitem>
- <remark>Assignee is: claprun</remark>
- <remark>JIRA is Closed</remark>
- <para>
- An inconsistency in how portlets are handled across different part of the
administration interface resulted in an error when remote portlets were added to a
category from the "Portlet" tab of the Application Registry. The
inconsistency has now be resolved and it should be now possible to properly display remote
portlets regardless of how they were added to categories.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-983 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-983">JBEPP-983<...
+ <listitem>
+
+ <remark>Assignee is: claprun</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ An inconsistency in how portlets are handled across different part of the
administration interface resulted in an error when remote portlets were added to a
category from the "Portlet" tab of the Application Registry. The inconsistency
has now be resolved and it should be now possible to properly display remote portlets
regardless of how they were added to categories.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-985 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-985">JBEPP-985<...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-985 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-985">JBEPP-985<...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
DateTimeValidator.java had an unnecessary check where the date input value
needed to match the (not localized) DATETIME_REGEX. This superfluous requirement caused
localized date input to fail. The fix removes the DATETIME_REGEX, which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1032 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1032">JBEPP-1032&...
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1032 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1032">JBEPP-1032&...
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
A bug was discovered where a transaction commit related to IDM database
operations was not placed within a final() block. Any misconfiguration, or operation
failure, could cause the database connection to remain open. The fix ensures the
transaction commit related to IDM database operations is placed within a final() block,
which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1048 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1048">JBEPP-1048&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-Site Scripting (XSS) vulnerability was discovered in the Edit Page
> Container Title field. The vulnerability is fixed in this release.
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1048 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1048">JBEPP-1048&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-Site Scripting (XSS) vulnerability was discovered in the Edit Page
> Container Title field. The vulnerability is fixed in this release. <ulink
url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo...
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1049 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1049">JBEPP-1049&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-site Scripting (XSS) vulnerability was discovered in the New Node
label. The vulnerability has been removed in this release.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1049 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1049">JBEPP-1049&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-site Scripting (XSS) vulnerability was discovered in the New Node
label. The vulnerability has been removed in this release. <ulink
url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo...
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1050 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1050">JBEPP-1050&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-site Scripting (XSS) vulnerability was discovered in the RSS reader
gadget. The vulnerability has been fixed in this release.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1050 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1050">JBEPP-1050&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-site Scripting (XSS) vulnerability was discovered in the RSS reader
gadget. The vulnerability has been fixed in this release. <ulink
url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo...
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1067 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1067">JBEPP-1067&...
- </term>
- <listitem>
- <remark>Assignee is: bdaw</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1067 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1067">JBEPP-1067&...
+ <listitem>
+
+ <remark>Assignee is: bdaw</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
Only users from the LDAP database were shown in organization management if
LDAP did not support sorting. The fix changes the logging level to INFO in PicketLink
IDM.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1082 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1082">JBEPP-1082&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1082 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1082">JBEPP-1082&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
If gadget restrict access to specific group, it was accessible for not
members in Dashboard and page editing.
Now users cannot add restricted gadget.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1148 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1148">JBEPP-1148&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1148 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1148">JBEPP-1148&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
Activating JRMP configuration in JBoss EPP 5.1.x (or EPP based products)
produced a large quantity of JMX/RMI logs in stdout/stderr. The JRMP agent had logging set
to FINE, which resulted in verbose log information. The fix removes the embedded logger
configuration, which results in the JBoss Enterprise Application Platform server log
configuration being used for logging.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1150 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1150">JBEPP-1150&...
- </term>
- <listitem>
- <remark>Assignee is: mputz</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1150 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1150">JBEPP-1150&...
+ <listitem>
+
+ <remark>Assignee is: mputz</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
An invisible navigation node was displayed in the Sitemap portlet when the
parent node was expanded (not with Expand All button). The workaround described in the
linked JIRA has been implemented in this release, which corrects the originally reported
issue.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1167 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1167">JBEPP-1167&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1167 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1167">JBEPP-1167&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
A problem with regard to the location of token keys prevented Gadgets from
working in load-balanced clustered portal environments. Token keys have been moved to a
location accessible by all load-balanced clustered portal instances. Gadgets can now be
used as intended.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1196 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1196">JBEPP-1196&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
- A problem with UploadService was causing the MIME type of .rtf files extracted
from DiskFileItem in Apache as "text/rtf". The value should have been
extracted as "application/rtf", which caused problems for applications
dependent on correct MIME type information. The fix corrects the MIME type encoding, and
ensures .rtf files are set with the MIME type "application/rtf".
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1196 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1196">JBEPP-1196&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ A problem with UploadService was causing the MIME type of .rtf files extracted
from DiskFileItem in Apache as "text/rtf". The value should have been extracted
as "application/rtf", which caused problems for applications dependent on
correct MIME type information. The fix corrects the MIME type encoding, and ensures .rtf
files are set with the MIME type "application/rtf".
+
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1221 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1221">JBEPP-1221&...
- </term>
- <listitem>
- <remark>Assignee is: mwringe</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1221 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1221">JBEPP-1221&...
+ <listitem>
+
+ <remark>Assignee is: mwringe</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
A problem with the GroupManagement.java isAdministrator method caused a
NullPointerException when the Organization Portlet is placed on a page and an anonymous
user tries to access it. The fix changes the behavior of isAdministrator for anonymous
users, which fixes the issue.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1241 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1241">JBEPP-1241&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- A Cross-site Scripting (XSS) vulnerability was discovered in the
UIFormDateTimeInput component. The vulnerability has been fixed in this release.
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1241 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1241">JBEPP-1241&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ A Cross-site Scripting (XSS) vulnerability was discovered in the
UIFormDateTimeInput component. The vulnerability has been fixed in this release. <ulink
url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo...
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1243 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1243">JBEPP-1243&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- Group descriptions text entered by users was not properly protected from XSS
attacks. It was possible to execute arbitrary Javascript if a user had permissions to
enter a group description. The group description field has been protected to not execute
any Javascript, which resolves the issue.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1243 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1243">JBEPP-1243&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
+ Group descriptions text entered by users was not properly protected from XSS
attacks. It was possible to execute arbitrary Javascript if a user had permissions to
enter a group description. The group description field has been protected to not execute
any Javascript, which resolves the issue. <ulink
url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo...
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1293 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1293">JBEPP-1293&...
- </term>
- <listitem>
- <remark>Assignee is: kenfinni</remark>
- <remark>JIRA is Closed</remark>
- <para>
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1293 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1293">JBEPP-1293&...
+ <listitem>
+
+ <remark>Assignee is: kenfinni</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() did not
correctly handle exceptions. Exceptions that typically occurred during during afterPhase()
were truncated (for example StaleObjectStateException in Hibernate commit). The Seam
exception handler was not notified of the truncated exceptions therefore the application
moves to a next page instead of an error page. The fix ensures
org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() catches exceptions and
passes them to Seam exception handler (for example, org.jboss.seam.jsf.SeamPhaseListener).
Because exceptions are handled correctly, the Seam exception handler displays and error
page given the appropriate conditions.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1310 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1310">JBEPP-1310&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
- If the Opera browser is used to access the portal home page, a Javascript
Uncaught exception is raised: "TypeError: 'Browser.setOpacity'
is not a function". The fix incorporates a verified customer-submitted patch to
Browser.js, which allows Opera browsers to access the portal home page.
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1310 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1310">JBEPP-1310&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ If the Opera browser is used to access the portal home page, a Javascript
Uncaught exception is raised: "TypeError: 'Browser.setOpacity' is not a
function". The fix incorporates a verified customer-submitted patch to Browser.js,
which allows Opera browsers to access the portal home page.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1319 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1319">JBEPP-1319&...
- </term>
- <listitem>
- <remark>Assignee is: claprun</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1319 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1319">JBEPP-1319&...
+ <listitem>
+
+ <remark>Assignee is: claprun</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
If the WSRP consumer was refreshed and activated, WSRP selfv2 prevented the
server from starting when it was rebooted. The only way to work around this issue was to
perform a force quit. The fix adds a &lt;value-param&gt; configuration
option to the main WSRP configuration. consumersInitDelay provides a way to specify a
delayed start (configurable, in seconds) of the ConsumerRegistry, which prevents a
deadlock situation while the self consumers wait for the producer WSDL to be published.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1324 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1324">JBEPP-1324&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1324 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1324">JBEPP-1324&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
It was found that the invoker servlets, deployed by default via
httpha-invoker, only performed access control on the HTTP GET and POST
methods, allowing remote attackers to make unauthenticated requests by
@@ -435,70 +629,102 @@
default installations unless an administrator has misconfigured the
security interceptor or disabled it. (CVE-2011-4085)
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1331 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1331">JBEPP-1331&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <para>
- When a portal host name contained the word "portal" in the
name, gadgets were not displayed and a TemplateRuntimeException would occur. The fix adds
functionality to several portal components which allows for the word
"portal" in the host name.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1331 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1331">JBEPP-1331&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ When a portal host name contained the word "portal" in the name,
gadgets were not displayed and a TemplateRuntimeException would occur. The fix adds
functionality to several portal components which allows for the word "portal" in
the host name.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1336 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1336">JBEPP-1336&...
- </term>
- <listitem>
- <remark>Assignee is: theute</remark>
- <remark>JIRA is Closed</remark>
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1336 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1336">JBEPP-1336&...
+ <listitem>
+
+ <remark>Assignee is: theute</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <warning>
+ <title>Not Public Yet - RHT+eXo</title>
+ <para>
It was found that the GateIn Portal contained verb-specific security
constraints. As a result, authentication and authorization were only correctly applied to
requests made using the GET and POST HTTP verbs. The GateIn Portal application does not
allow a user to trigger any action using HTTP verbs other than POST and GET, so this issue
did not expose an exploitable security flaw. As a defence-in-depth measure, the
verb-specific security constraints have been removed. Authentication and authorization now
correctly apply to requests made using all HTTP verbs.
</para>
- </warning>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1351 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1351">JBEPP-1351&...
- </term>
- <listitem>
- <remark>Assignee is: hfnukal</remark>
- <remark>JIRA is Closed</remark>
- <para>
- The org.gatein.sso.agent.login.SSOLoginModule contains the common options
"portal" and "realmName" as offered in other
LoginModule classes. In the packaged gatein-jboss-beans.xml, this login module did not
have these options. This caused problems when a customer wanted to implement SSO on a
different portal container (for example in ecmdemo). The fix includes these common options
in gatein-jboss-beans.xml, which resolves the issue.
+ </warning>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1351 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1351">JBEPP-1351&...
+ <listitem>
+
+ <remark>Assignee is: hfnukal</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
+ The org.gatein.sso.agent.login.SSOLoginModule contains the common options
"portal" and "realmName" as offered in other LoginModule classes. In
the packaged gatein-jboss-beans.xml, this login module did not have these options. This
caused problems when a customer wanted to implement SSO on a different portal container
(for example in ecmdemo). The fix includes these common options in gatein-jboss-beans.xml,
which resolves the issue.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1357 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1357">JBEPP-1357&...
- </term>
- <listitem>
- <remark>Assignee is: claprun</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1357 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1357">JBEPP-1357&...
+ <listitem>
+
+ <remark>Assignee is: claprun</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The Web Services for Remote Portlet (WSRP) configuration files for consumers and
producer were previously only looked for in the WSRP extension archive. This resulted in
extra configuration complexity for customers who wanted to edit the configuration
directives for WSRP consumers and producer. The fix implements changes to the WSRP
integration point that will now also look for WSRP configuration files in the conf/gatein
directory of the active JBoss AS profile.
</para>
- </listitem>
- </varlistentry>
-<!--
https://issues.jboss.org/browse/JBEPP-1361 --> <varlistentry>
- <term>
- <ulink
url="https://issues.jboss.org/browse/JBEPP-1361">JBEPP-1361&...
- </term>
- <listitem>
- <remark>Assignee is: mposolda</remark>
- <remark>JIRA is Closed</remark>
- <para>
+
+ </listitem>
+ </varlistentry>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-1361 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1361">JBEPP-1361&...
+ <listitem>
+
+ <remark>Assignee is: mposolda</remark>
+
+
+ <remark>JIRA is Closed</remark>
+
+
+ <para>
The JBoss Clustered Single Sign On (SSO) Valve must authenticate on all
clustered nodes using the same password. The login process in Enterprise Portal Platform
differed from normal authentication methods, and customers had to bypass standard
authentication by enabling BASIC authentication, or patch login.jsp as described in the
Reference Guide. The fix introduces PortalClusteredSSOSupportValve, which removes the
patching and workarounds customers had to implement in earlier versions of the product,
and increases overall platform security.
</para>
- </listitem>
- </varlistentry>
+
+ </listitem>
+ </varlistentry>
+
</variablelist>
Modified: epp/docs/branches/5.2/Release_Notes/publican.cfg
===================================================================
--- epp/docs/branches/5.2/Release_Notes/publican.cfg 2011-12-08 03:29:08 UTC (rev 8209)
+++ epp/docs/branches/5.2/Release_Notes/publican.cfg 2011-12-08 04:49:17 UTC (rev 8210)
@@ -7,4 +7,4 @@
show_remarks: 1
cvs_branch: DOCS-RHEL-6
cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist
-cvs_pkg: JBoss_Enterprise_Portal_Platform-5.2.0_BETA_Release_Notes-5.2-web-__LANG__
+cvs_pkg: JBoss_Enterprise_Portal_Platform-5.2.0_Release_Notes-5.2-web-__LANG__