Author: jaredmorgs Date: 2012-04-23 23:01:05 -0400 (Mon, 23 Apr 2012) New Revision: 8704 Modified: epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/5.2.1_Release_Notes.xml epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/Book_Info.xml epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/Revision_History.xml epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/known.xml epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/needinfo.xml epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/resolved.xml Log: Final changes for Release Notes 5.2.1 Modified: epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/5.2.1_Release_Notes.xml =================================================================== --- epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/5.2.1_Release_Notes.xml 2012-04-20 05:39:09 UTC (rev 8703) +++ epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/5.2.1_Release_Notes.xml 2012-04-24 03:01:05 UTC (rev 8704) @@ -1,6 +1,5 @@ <?xml version='1.0' encoding='UTF-8'?> -<!-- This document was created with Syntext Serna Free. --> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!-- This document was created with Syntext Serna Free. --><!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % BOOK_ENTITIES SYSTEM "5.2.1_Release_Notes.ent"> %BOOK_ENTITIES; ]> @@ -98,7 +97,7 @@ </row> <row> <entry>eXo JCR</entry> - <entry>1.14.6GA</entry> + <entry>1.14.6-GA</entry> </row> <row> <entry>Apache Shindig</entry> @@ -186,12 +185,8 @@ </row> <row> <entry>GateIn Management</entry> - <entry>1.0.0-GA</entry> + <entry>1.0.1-GA</entry> </row> - <row> - <entry>Gatein JON Plugin</entry> - <entry>1.0.0</entry> - </row> </tbody> </tgroup> </table> @@ -206,7 +201,7 @@ <varlistentry> <term>Gatein JON Plugin</term> <listitem> - <para>The Gatein JON plugin allows the portal to interact with JBoss Operations Network. The plugin captures portlet and site statistics.</para> + <para>The Gatein JON plugin allows the portal to interact with JBoss Operations Network. The plugin captures portlet and site statistics. The latest version of the JON plugin is v1.0.1</para> </listitem> </varlistentry> </variablelist> Modified: epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/Book_Info.xml =================================================================== --- epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/Book_Info.xml 2012-04-20 05:39:09 UTC (rev 8703) +++ epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/Book_Info.xml 2012-04-24 03:01:05 UTC (rev 8704) @@ -9,7 +9,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.1</edition> - <pubsnumber>50</pubsnumber> + <pubsnumber>100</pubsnumber> <abstract> <para> These release notes contain important information related to JBoss Enterprise Portal Platform &VZ;, and the Site Publisher plug-in 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/tags/EPP_5_2_1_GA/Release_Notes/en-US/Revision_History.xml =================================================================== --- epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/Revision_History.xml 2012-04-20 05:39:09 UTC (rev 8703) +++ epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/Revision_History.xml 2012-04-24 03:01:05 UTC (rev 8704) @@ -7,33 +7,17 @@ <title>Revision History</title> <simpara> <revhistory> - <revision> - <revnumber>5.2.1-50</revnumber> - <date>Tue Apr 17 2012</date> + <revnumber>5.2.1-100</revnumber> + <date>Tue Apr 24 2012</date> <author> <firstname>Jared</firstname> <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Final Draft Release Notes prepared for JBoss Enterprise Portal Platform 5.2.1 GA sign-off.</member> - </simplelist> - </revdescription> - </revision> - - <revision> - <revnumber>5.2.0-101</revnumber> - <date>Thu Dec 14 2011</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> <email>jmorgan [at] redhat [dot] com</email> </author> <revdescription> <simplelist> - <member>Release Notes prepared for JBoss Enterprise Portal Platform 5.2.0 GA.</member> + <member>Release Notes prepared for JBoss Enterprise Portal Platform 5.2.1 GA.</member> </simplelist> </revdescription> </revision> Modified: epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/known.xml =================================================================== --- epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/known.xml 2012-04-20 05:39:09 UTC (rev 8703) +++ epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/known.xml 2012-04-24 03:01:05 UTC (rev 8704) @@ -1,70 +1,36 @@ -<?xml version='1.0'?> +<?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> - -<chapter id = "known_issues"> - <title>Known Issues</title> - - <para> +<chapter id="known_issues"> + <title>Known Issues</title> + <para> The following issues are known to exist in this release of JBoss Enterprise Portal Platform, and will be fixed in a subsequent release. </para> - <remark> - Do some of these issues look more like <emphasis>Resolved Issues</emphasis>? If they do, its because the ticket has not been set to the correct - Resolved Issue status (VERIFIED, CLOSED). - </remark> - <variablelist> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=807279"><... - Support WSRP applications for Export/Import</term> - <listitem> - <remark>Status: NEW</remark> - <para> + <remark> Do some of these issues look more like <emphasis>Resolved Issues</emphasis>? If they do, its because the ticket has not been set to the correct Resolved Issue status (VERIFIED, CLOSED). </remark> + <variablelist> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=807279"> + <citetitle>BZ#807279</citetitle> + </ulink> - Support WSRP applications for Export/Import</term> + <listitem> + <remark>Status: NEW</remark> + <para> When WSRP is added to a page, and a user attempts to export the page using the portal management functions, an exception displays stating WSRP is not supported. This issue is being investigated, and will be included in a future release of the portal. There is no workaround to this issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=809141"><... - Sample extension datasource uses local-tx-datasource type</term> - <listitem> - <remark>Status: NEW</remark> - <para> - It was discovered that the sample datasource file for portal extensions -<filename>jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml</filename> specifies the incorrect datasource type for IDM. It should be no-tx-datasource for IDM and + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=809141"> + <citetitle>BZ#809141</citetitle> + </ulink> - Sample extension datasource uses local-tx-datasource type</term> + <listitem> + <remark>Status: NEW</remark> + <para> + It was discovered that the sample datasource file for portal extensions +<filename>jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml</filename> specifies the incorrect datasource type for IDM. It should be no-tx-datasource for IDM and local-tx-datasource for JCR, instead of local-tx-datasource for both directive blocks. To work around the issue, define the datasource type manually, following the guidelines in this Release Note. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794461"><... - Patch required for CVE-2012-0818</term> - <listitem> - <remark>Status: ON_QA</remark> - <para> - It was found that RESTEasy was vulnerable to XML External Entity (XXE) attacks. If a remote attacker submitted a request containing an external XML entity to a RESTEasy endpoint, the entity would be resolved, allowing the attacker to read files accessible to the user running the application server. This flaw affected DOM (Document Object Model) Document and JAXB (Java Architecture for XML Binding) input. (<ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=785631">CVE...>) - </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=806965"><... - PortletModes and WindowStates are not properly broadcasting events in webui</term> - <listitem> - <remark>Status: ON_QA</remark> - <para> - It was discovered that an issue with exo.portal.webui.portal caused pre-configured window states (maximized, normal, minimized) to be ignored when navigating between portlets. This caused the maximized portlet to hide the other portlets that were set to normal or minimized. Refreshing the page forced the window state to behave correctly. The fix provides an updated version of exo.portal.webui.portal with improvements to window state behavior. The originally reported issue is resolved as a result of these improvements. - </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=805875"><... - WSRP configuration files to be picked up from gatein.conf.dir on Windows machine</term> - <listitem> - <remark>Status: ON_QA</remark> - <para> - The WSRP extension didn't properly compute paths to the configuration files, resulting in the extension not being able to find the configuration files on Windows systems. The path computing algorithm has been changed to resolve this issue. - </para> - </listitem> -</varlistentry> - - </variablelist> + </listitem> + </varlistentry> + </variablelist> </chapter> Modified: epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/needinfo.xml =================================================================== --- epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/needinfo.xml 2012-04-20 05:39:09 UTC (rev 8703) +++ epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/needinfo.xml 2012-04-24 03:01:05 UTC (rev 8704) @@ -15,15 +15,5 @@ </remark> <variablelist> -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=810345"><... - one-off patch: File name is not displayed correctly if it contains Portuguese accent characters during uploading</term> - <listitem> - <para>The status is ASSIGNED, assigned to ghu(a)redhat.com.&lt;/para&gt; - <para> - It was discovered that an issue with exo.portal.component.web.server caused file name is not displayed correctly if it contains Portuguese accent characters during uploading. The fix provides an updated version of exo.portal.component.web.server with improvements to special international characters encoding. The originally reported issue is resolved as a result of these improvements. - </para> - </listitem> -</varlistentry> - </variablelist> </chapter> Modified: epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/resolved.xml =================================================================== --- epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/resolved.xml 2012-04-20 05:39:09 UTC (rev 8703) +++ epp/docs/tags/EPP_5_2_1_GA/Release_Notes/en-US/resolved.xml 2012-04-24 03:01:05 UTC (rev 8704) @@ -1,526 +1,606 @@ -<?xml version='1.0'?> +<?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> - -<chapter id = "resolved"> - <title>Resolved Issues</title> - <para> +<chapter id="resolved"> + <title>Resolved Issues</title> + <para> The following issues have been resolved in this release of JBoss Enterprise Portal Platform. </para> - <variablelist> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=807626"><... - Producer registration error when producer is set to not use registrations</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - EPP's WSRP producer uses a special registration to track portlet contexts when registration is disabled. This registration was improperly initialized resulting in registration errors when registration is disabled on the producer. The initialization of the registration has been fixed and a fix has been put in place to repair this improperly initialized registration from previous EPP versions. + <variablelist> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=807626"> + <citetitle>BZ#807626</citetitle> + </ulink> - Producer registration error when producer is set to not use registrations</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> + EPP&apos;s WSRP producer uses a special registration to track portlet contexts when registration is disabled. This registration was improperly initialized resulting in registration errors when registration is disabled on the producer. The initialization of the registration has been fixed and a fix has been put in place to repair this improperly initialized registration from previous EPP versions. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=798839"><... - Convert Installation Guide to Task Based Format</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=798839"> + <citetitle>BZ#798839</citetitle> + </ulink> - Convert Installation Guide to Task Based Format</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> The Installation Guide has undergone extensive rework in this release, and has been converted to a task-based format. The Site Publisher Installation Guide has been merged into the Installation Guide to keep installation information for all platform elements together in one source. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794070"><... - Unable to remove DB users if LDAP store is not read-only</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794070"> + <citetitle>BZ#794070</citetitle> + </ulink> - Unable to remove DB users if LDAP store is not read-only</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> It was discovered that an error in the PicketLink IDM caused a problem with removing an LDAP User from a read/write user store, when the user was not present in the IDM database. The fix introduces logic improvements to user management that ensures a user can only be removed from the correct identity store. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794428"><... - Deleting a group causes IdentityException with openldap</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794428"> + <citetitle>BZ#794428</citetitle> + </ulink> - Deleting a group causes IdentityException with openldap</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> If a nested IDM OpenLDAP child group was deleted from its parent, an IdentityException occurred because OpenLDAP IDM removed the child group but not the parent-child relationship. The fix improves the logic behind child group deletion to ensure group associations are removed prior to deleting a group. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794436"><... - Duplicated last entry in the user list of the organization portlet</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - A design limitation in the Organization API caused inefficient paginated user queries. This was identified when user duplication occurred across LDAP and within the database, and there was different user data contained in these databases. The portal displayed the last entry in the returned query several times, which caused confusion when interpreting the query results. The fix introduces a configuration switch "countPaginatedUsers", which is configurable in the idm-configuration.xml file. Set the value to false to activate the switch, and improve query accuracy. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794436"> + <citetitle>BZ#794436</citetitle> + </ulink> - Duplicated last entry in the user list of the organization portlet</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> + A design limitation in the Organization API caused inefficient paginated user queries. This was identified when user duplication occurred across LDAP and within the database, and there was different user data contained in these databases. The portal displayed the last entry in the returned query several times, which caused confusion when interpreting the query results. The fix introduces a configuration switch &quot;countPaginatedUsers&quot;, which is configurable in the idm-configuration.xml file. Set the value to false to activate the switch, and improve query accuracy. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793319"><... - Remove IP addresses from picketlink msad example config files</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - It was discovered that the Microsoft Active Directory (MSAD) configuration files (<filename>picketlink-idm-msad-config.xml</filename> and <filename>picketlink-idm-msad-readonly-config.xml</filename>) contained a providerURL property with an IP address specified. The IP address was interpreted by customers as required and mandatory, instead of being interpreted as a value that needed to be changed to an IP address used in the customer's implementation. The fix replaces the numerical IP address with replaceable values that are more prescriptive to users, which corrects the originally reported issue. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793319"> + <citetitle>BZ#793319</citetitle> + </ulink> - Remove IP addresses from picketlink msad example config files</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> + It was discovered that the Microsoft Active Directory (MSAD) configuration files (<filename>picketlink-idm-msad-config.xml</filename> and <filename>picketlink-idm-msad-readonly-config.xml</filename>) contained a providerURL property with an IP address specified. The IP address was interpreted by customers as required and mandatory, instead of being interpreted as a value that needed to be changed to an IP address used in the customer&apos;s implementation. The fix replaces the numerical IP address with replaceable values that are more prescriptive to users, which corrects the originally reported issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793910"><... - GTNPORTAL-1940 calender doesnt disappear if tab is used for navigation</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793910"> + <citetitle>BZ#793910</citetitle> + </ulink> - GTNPORTAL-1940 calender doesnt disappear if tab is used for navigation</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> It was discovered that when users tabbed away from the calendar field, the calendar dialog persisted. Users had to click outside the calendar field to close the calendar dialog. The fix introduces updated behavior which ensures the calendar dialog closes on tab navigation away from the field. This corrects the originally reported issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794181"><... - Some first name and last name parameters are reversed in Japanese message bundle of UserInfoPortlet</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - An issue was found in UserInfoPortlet concerning the -"firstname" and "lastname" Japanese field translations. The first name and last name field translations were swapped, which made it difficult for Japanese users to populate the correct fields with appropriate name data. The fix correct the labels for the firstname and lastname fields, which corrects the originally reported issue. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794181"> + <citetitle>BZ#794181</citetitle> + </ulink> - Some first name and last name parameters are reversed in Japanese message bundle of UserInfoPortlet</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> + An issue was found in UserInfoPortlet concerning the +&quot;firstname&quot; and &quot;lastname&quot; Japanese field translations. The first name and last name field translations were swapped, which made it difficult for Japanese users to populate the correct fields with appropriate name data. The fix correct the labels for the firstname and lastname fields, which corrects the originally reported issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794445"><... - Admin console does not display JBoss info: only OS info is shown</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794445"> + <citetitle>BZ#794445</citetitle> + </ulink> - Admin console does not display JBoss info: only OS info is shown</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> JON did not detect JBoss Enterprise Portal Platform as an altered JBoss Enterprise Application Platform. This caused the admin-console to not display metrics about the portal, and only display basic operating system information. The fix corrects JON to recognize the portal as a altered application platform. Metrics available for JBoss Enterprise Application Platform are now available for Enterprise Portal Platform. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794390"><... - List of users in group counts with users from all realms (paging is displayed, but no user)</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794461"> + <citetitle>BZ#794461</citetitle> + </ulink> - Patch required for CVE-2012-0818</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> + It was found that RESTEasy was vulnerable to XML External Entity (XXE) attacks. If a remote attacker submitted a request containing an external XML entity to a RESTEasy endpoint, the entity would be resolved, allowing the attacker to read files accessible to the user running the application server. This flaw affected DOM (Document Object Model) Document and JAXB (Java Architecture for XML Binding) input. (<ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=785631">CVE...>) + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794390"> + <citetitle>BZ#794390</citetitle> + </ulink> - List of users in group counts with users from all realms (paging is displayed, but no user)</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> In some methods in PicketLink IDM, the correct identity realm information was not used in the hibernate query. This issue was fixed in PicketLink and included in this release of the platform. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794386"><... - Update documentation to describe how to replace HSQLDB in EPP</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794386"> + <citetitle>BZ#794386</citetitle> + </ulink> - Update documentation to describe how to replace HSQLDB in EPP</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> It was discovered that there was insufficient information in the Installation Guide regarding how to replace the default Hypersonic Database (HSQLDB) with a certified database that Red Hat supports. Detailed steps have been added to the Database Configuration section of the guide, which explain how to replace HSQLDB, and the requirements JBoss Enterprise Portal Platform has regarding separate databases for JCR and IDM. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794440"><... - Docs: Instructions on how to set up the https connector are incomplete</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794440"> + <citetitle>BZ#794440</citetitle> + </ulink> - Docs: Instructions on how to set up the https connector are incomplete</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> Gadgets require HTTPS to be configured correctly in order to operate. This requirement was not clearly documented in the Installation Guide, which caused configuration issues for customers. Instructions from a KBase article have been incorporated into the Installation Guide, with clarifying links to other JBoss Middleware product documentation for background info on keystore and truststore configuration. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794466"><... - LOGIN_URL contains a line break in CAS integration document</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - A problem was identified with an important file path in the "Redirect to CAS" procedure of the Reference Guide. A break in the LOGIN_URL parameter value caused issues when the code sample was copied, causing the code sample to be invalid when used verbatim in actual configuration. The LOGIN_URL value has been reformatted to a single line, which removes the space and corrects the originally reported issue. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794466"> + <citetitle>BZ#794466</citetitle> + </ulink> - LOGIN_URL contains a line break in CAS integration document</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> + A problem was identified with an important file path in the &quot;Redirect to CAS&quot; procedure of the Reference Guide. A break in the LOGIN_URL parameter value caused issues when the code sample was copied, causing the code sample to be invalid when used verbatim in actual configuration. The LOGIN_URL value has been reformatted to a single line, which removes the space and corrects the originally reported issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793259"><... - IE6 User Interface problems</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793259"> + <citetitle>BZ#793259</citetitle> + </ulink> - IE6 User Interface problems</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> A problem affecting Microsoft Internet Explorer 6 caused portal javascript module messages to remain in the window status area after the module had successfully loaded. This caused confusion if a customer was not aware a module had loaded, and saw the error message. The fix corrects the issue by clearing the window.status message after a javascript module is loaded. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793639"><... - Create additional portal objects for external groups</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793639"> + <citetitle>BZ#793639</citetitle> + </ulink> - Create additional portal objects for external groups</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml</filename>, which imports the configuration stored in the initializer-configuration.xml file. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793804"><... - logged in user's role change doesn't take effect on the UI after a certain amount of "cache" time or user logs out and re-login.</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - It was discovered that changing memberships of already authenticated users did not immediately take effect. If a user had administrative membership revoked, and remained logged onto the portal, the privileges were still accessible for up to 30 minutes until the user permissions cache was refreshed. This could permit the user to perform undesirable actions in the portal. The fix introduces a new listener "MembershipUpdateListener" which has been added to <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/organization/organization-configuration.xml</filename> directive file. The listener immediately updates authenticated user memberships based on information in the ConversationRegistry. Changes to user memberships now take effect immediately, which corrects the originally reported issue. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793804"> + <citetitle>BZ#793804</citetitle> + </ulink> - logged in user&apos;s role change doesn&apos;t take effect on the UI after a certain amount of &quot;cache&quot; time or user logs out and re-login.</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> + It was discovered that changing memberships of already authenticated users did not immediately take effect. If a user had administrative membership revoked, and remained logged onto the portal, the privileges were still accessible for up to 30 minutes until the user permissions cache was refreshed. This could permit the user to perform undesirable actions in the portal. The fix introduces a new listener &quot;MembershipUpdateListener&quot; which has been added to <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/organization/organization-configuration.xml</filename> directive file. The listener immediately updates authenticated user memberships based on information in the ConversationRegistry. Changes to user memberships now take effect immediately, which corrects the originally reported issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794235"><... - The display name of login user should be configurable in UIUserInfoPortlet</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794235"> + <citetitle>BZ#794235</citetitle> + </ulink> - The display name of login user should be configurable in UIUserInfoPortlet</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> The way the display name of authenticated users presented in portal screens used the firstName lastName format (commonly referred to as Western Order). Customers in regions where Eastern Order is prevalent reported issues with configuring upper-name requirements in portal UI screens. The fix introduces the Display Name (displayName) field, which is available in all UI screens. When configuring a user account, the user can specify their preferred display name, which overrides the fullName value retrieved by default. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794394"><... - Invalid page title of page causes unability to edit node</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794394"> + <citetitle>BZ#794394</citetitle> + </ulink> - Invalid page title of page causes unability to edit node</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> An issue with field value validation in page title fields caused angle brackets to be added verbatim to the page title. These verbatim characters resulted in portal page errors because the angle brackets were not substituted with HTML character references when the form was saved. The fix introduces NoHTMLTagValidator logic in page title fields, which prevents verbatim angle brackets from being entered into the field. Angle brackets can be included in titles, providing the correct HTML character references are declared: &amp;lt; and &amp;gt; </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794376"><... - Navigation labels are shortened but not looking good in multibyte languages</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794376"> + <citetitle>BZ#794376</citetitle> + </ulink> - Navigation labels are shortened but not looking good in multibyte languages</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> To fit on the user interface, navigation node names are cut after a certain number of characters. Cutting happened after measuring the length of the encoded string. Some encoded characters were cut in the middle, resulting in incorrect characters on the screen. The string is now measured and cut before the encoding takes place. Navigation nodes are now properly shortened. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=803544"><... - ViewExpiredException when using Portlet Bridge over WSRP with WS Security</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=803544"> + <citetitle>BZ#803544</citetitle> + </ulink> - ViewExpiredException when using Portlet Bridge over WSRP with WS Security</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> The cookie session handler was not being set on each request from the producer and the consumer when ws-security was enabled. A session was created on each request, and any portlets that relied on sessions would not function properly. The fix implements changes to the order of the web service handlers that ensure the session is properly added on each invocation between the consumer and producer. Sessions now work properly with WSRP when WS-Security is enabled </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793666"><... - WSRP admin interface graphics has minor problems</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=805875"> + <citetitle>BZ#805875</citetitle> + </ulink> - WSRP configuration files to be picked up from gatein.conf.dir on Windows machine</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> + The WSRP extension didn&apos;t properly compute paths to the configuration files, resulting in the extension not being able to find the configuration files on Windows systems. The path computing algorithm has been changed to resolve this issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793666"> + <citetitle>BZ#793666</citetitle> + </ulink> - WSRP admin interface graphics has minor problems</term> + <listitem> + <remark>Status: VERIFIED</remark> + <para> The WSRP administration portlet user interface has been slightly improved to resolve some rendering errors in older browsers. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793571"><... - GTNPORTAL-1673 make UI validation regular expressions configurable by users</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793571"> + <citetitle>BZ#793571</citetitle> + </ulink> - GTNPORTAL-1673 make UI validation regular expressions configurable by users</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> Several fields requiring user names were previously validated using hardcoded logic, which prevented users from easily changing what user name formats were acceptable for their requirements. The fix implements ExpressionValidator, which permits user name validation changes without having to customize the source code. The validator allows users to specify the format required for valid user names, which overrides the default field validation present in the portal. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794400"><... - able to save wsrp producer property with non-valid name</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - Values input in the registration properties field in + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794400"> + <citetitle>BZ#794400</citetitle> + </ulink> - able to save wsrp producer property with non-valid name</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + Values input in the registration properties field in the Producer configuration part of the WSRP administration portlet were not properly validated. This resulted in errors further down the stack (in particular at the persistence level), an inconsistent user interface, and possible XSS vulnerabilities. Input is now properly validated and errors should now be caught much earlier, rherefore avoiding invalid values to propagate to lower levels of the WSRP service. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794350"><... - Breadcrumb Portlet doesn't update when a language change occurs</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794350"> + <citetitle>BZ#794350</citetitle> + </ulink> - Breadcrumb Portlet doesn&apos;t update when a language change occurs</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> A problem with the breadcrumb menu caused the breadcrumb menu in portal screens to remain in the originally selected language after users selected their preferred language. The fix introduces improvements to the breadcrumb code that refresh the breadcrumb menu when a users selects their preferred language. This fixes the originally reported issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794369"><... - Gadgets without titles not handled properly in Application Registry</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794369"> + <citetitle>BZ#794369</citetitle> + </ulink> - Gadgets without titles not handled properly in Application Registry</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> It was discovered that a Gadget could be added with an empty title. This caused the gadget to become unusable because all gadgets must have a title. The fix ensures that the title field is completed correctly prior to the gadget being saved, therefore fixing the issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794463"><... - ResourceIDs are sometimes lost when serving portlet resources</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794463"> + <citetitle>BZ#794463</citetitle> + </ulink> - ResourceIDs are sometimes lost when serving portlet resources</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> It was discovered that ResourceIDs were sometimes lost when serving resources during a portlet invocation. This would cause the resourceIds to be null, resulting in resources not being properly fetched. The fix implements logic changes that now provide additional checks within the portal for resourceIDs. Resources now function more reliably, particularly when using the portlet bridge over WSRP. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794384"><... - Unicode characters handling problem</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794384"> + <citetitle>BZ#794384</citetitle> + </ulink> - Unicode characters handling problem</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> HTTP Request parameters were retrieved before the character encoding was set to UTF-8. The default character encoding of ISO-8859-1 was used instead, leading to corrupted characters. The fix ensures character encoding is set to UTF-8 before Request parameters are accessed. Correct unicode characters are now returned in form posts. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793938"><... - Replicated seesion is corrupted in Portlet Bridge Seam application</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - An issue with de-serialization discovered in org.gatein.pc.api.PortletInvokerException caused the -Clustered Seam Booking demo Portlet to throw an exception when the user session node failed or shutdown, and the user session transferred to another node. The fix implements changes to org.gatein.pc.api.PortletInvokerException that calls defaultReadObject() when de-serializing PortalIdentity. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793938"> + <citetitle>BZ#793938</citetitle> + </ulink> - Replicated session is corrupted in Portlet Bridge Seam application</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + An issue with de-serialization discovered in org.gatein.pc.api.PortletInvokerException caused the +Clustered Seam Booking demo Portlet to throw an exception when the user session node failed or shutdown, and the user session transferred to another node. The fix implements changes to org.gatein.pc.api.PortletInvokerException that calls defaultReadObject() when de-serializing PortalIdentity. The Session is correctly restored for the Seam Booking portlet after the user session is transferred to an available node. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793999"><... - PBR-284: rich:simpleTogglePanel does not work when placing two portlets in a page</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793999"> + <citetitle>BZ#793999</citetitle> + </ulink> - PBR-284: rich:simpleTogglePanel does not work when placing two portlets in a page</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> An issue with how PortletBridge wrapped JavaScript files from RichFaces caused portlets to function incorrectly, and throw JavaScript errors. The fix correctly identifies the JavaScript files that require wrapping by PortletBridge using the LoadScriptStrategy ALL and WRAP_SCRIPTS true parameter values. RichFaces portlets now function correctly on Microsoft Internet Explorer and Chrome. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793387"><... - Administration portlets not accessible when reconnection to LDAP from another instance</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793387"> + <citetitle>BZ#793387</citetitle> + </ulink> - Administration portlets not accessible when reconnection to LDAP from another instance</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> A problem with the logic in OrganizationDatabaseInitializer caused issues with LDAP group mapping and permissions when the platform was executed for the first time. The fix introduces updated logic in NewPortalConfigListener, which ensures LDAP groups are correctly initialized, with all permission fields properly assigned. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793838"><... - Provide support for a newer JOSSO version</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - Due to a changed Java Open Single Sign On JOSSO agent API, it was only possible to upgrade JOSSO to v1.8.1. An upstream fix was applied to JBoss Enterprise Portal Platform which allows later JOSSO versions to be applied after v1.8.1. A changed JOSSO agent API between JOSSO versions v1.8.1 and v1.8.2 requires different packaging, which has changed some procedures. Refer to the updated procedures in the <citetitle>Reference Guide</citetitle> "Java Open Single Sign-On Project" section for more details. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793838"> + <citetitle>BZ#793838</citetitle> + </ulink> - Provide support for a newer JOSSO version</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + Due to a changed Java Open Single Sign On JOSSO agent API, it was only possible to upgrade JOSSO to v1.8.1. An upstream fix was applied to JBoss Enterprise Portal Platform which allows later JOSSO versions to be applied after v1.8.1. A changed JOSSO agent API between JOSSO versions v1.8.1 and v1.8.2 requires different packaging, which has changed some procedures. Refer to the updated procedures in the <citetitle>Reference Guide</citetitle> &quot;Java Open Single Sign-On Project&quot; section for more details. </para> - </listitem> -</varlistentry> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793956"> + <citetitle>BZ#793956</citetitle> + </ulink> - Support for system property substitution in PicketLink IDM configuration</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + Picketlink IDM did not support system property substitution in the configuration files. -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793956"><... - Support for system property substitution in PicketLink IDM configuration</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - Picketlink IDM did not support system property substitution in the configuration files. - -The fix implements parameters that allow system property substitution. Substitution is supported for every String element in the Picketlink IDM configuration file. The substitution operates in the same way as JBoss Enterprise Application Platform substitution. Usage examples follow. - -<itemizedlist> - <listitem> - <para>${property1} - Substitutes the system property &quot;property1&quot;.</para> - </listitem> - <listitem> - <para>${property1:defaultValue} - Substitutes the system property &quot;property1&quot;, and passes the &quot;defaultValue&quot; value if the system property is not set.</para> - </listitem> - <listitem> - <para>${property1,property2:defaultValue} - Substitutes the system property &quot;property1&quot;, then attempts to set the &quot;property2&quot; system property. If &quot;property1&quot; and &quot;property2&quot; are not set, fallback to &quot;defaultValue&quot;.</para> - </listitem> -</itemizedlist> +The fix implements parameters that allow system property substitution. Substitution is supported for every String element in the Picketlink IDM configuration file. The substitution operates in the same way as JBoss Enterprise Application Platform substitution. Usage examples follow. + +<itemizedlist> + <listitem> + <para>${property1} - Substitutes the system property &quot;property1&quot;.</para> + </listitem> + <listitem> + <para>${property1:defaultValue} - Substitutes the system property &quot;property1&quot;, and passes the &quot;defaultValue&quot; value if the system property is not set.</para> + </listitem> + <listitem> + <para>${property1,property2:defaultValue} - Substitutes the system property &quot;property1&quot;, then attempts to set the &quot;property2&quot; system property. If &quot;property1&quot; and &quot;property2&quot; are not set, fallback to &quot;defaultValue&quot;.</para> + </listitem> + </itemizedlist> </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794129"><... - Log level improvement in FallbackIdentityStoreRepository class (PicketLink IDM)</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794129"> + <citetitle>BZ#794129</citetitle> + </ulink> - Log level improvement in FallbackIdentityStoreRepository class (PicketLink IDM)</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> It was discovered that the Picketlink IDM FallbackIdentityStoreRepository class was using INFO logging instead of an elevated log level. Customers could miss important error information in the logs because INFO is commonly used for non-critical errors. The fix implements SEVERE logging category changes for all exceptions that are not propagated to the caller. For exceptions that are propagated to the caller, FINER logging is configured because these exceptions should be processed and logged by the caller. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794356"><... - Clicking on User management tabs can cause the "no results found" popup</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - A User Interface issue with the "No Result Found" pop-up caused it to display when a user first searched for a non-existent user string, then searched for a string that was known to exist. Users experienced issues with finding user records because the pop-up suggested there were no valid results when valid results existed. The fix implements changes to OrganizationManagementPortlet, which ensure the "No results found" pop-up is displayed only when no results are found. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794356"> + <citetitle>BZ#794356</citetitle> + </ulink> - Clicking on User management tabs can cause the &quot;no results found&quot; popup</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + A User Interface issue with the &quot;No Result Found&quot; pop-up caused it to display when a user first searched for a non-existent user string, then searched for a string that was known to exist. Users experienced issues with finding user records because the pop-up suggested there were no valid results when valid results existed. The fix implements changes to OrganizationManagementPortlet, which ensure the &quot;No results found&quot; pop-up is displayed only when no results are found. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794454"><... - Images are processed by PortalRequestHandler</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794454"> + <citetitle>BZ#794454</citetitle> + </ulink> - Images are processed by PortalRequestHandler</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> It was discovered that an incorrect mapping order in controller.xml caused PortalRequestHandler to process images. Because PortalRequestHandler was not designed to process images, incorrect HTTP header information was used for images. The fix corrects the mapping order in controller.xml so StaticResourceHandler is declared before PortalRequestHandler. This ensures the appropriate handler is called to manage images. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794456"><... - WebAppController needs to start RequestLifeCycle for every processing (including static resource processing)</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794456"> + <citetitle>BZ#794456</citetitle> + </ulink> - WebAppController needs to start RequestLifeCycle for every processing (including static resource processing)</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> A performance impact was discovered in the WebAppController that required RequestLifeCycle to be started for all processing, including static resources. Because RequestLifeCycle requires Hibernate transactions, this service needed to be started for all processing, which introduced a performance implication. The fix adds a new method (getRequireLifeCycle) to the WebRequestHandler class, which allows handlers to decide whether RequestLifeCycle is required to complete the transaction. Hibernate is only called for handlers sending requests to the portal, and not for handlers processing images. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794320"><... - Enable customization of LocalConfig service by extending existing implementations</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - It was discovered that many methods in LocaleConfigImpl, and + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794320"> + <citetitle>BZ#794320</citetitle> + </ulink> - Enable customization of LocalConfig service by extending existing implementations</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + It was discovered that many methods in LocaleConfigImpl, and LocaleConfigServiceImpl were declared final or private. Users were unable to reuse an existing implementation by extending and overriding the methods, and were forced to make a copy of the method to implement customized behavior. The fix removes the final declaration from these methods, and declares private methods as protected. This allows users to extend and override the default LocaleConfig implementation. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794437"><... - NullPointerException upgrading EPP from 5.1 to 5.2</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - After upgrading from EPP 5.1 to 5.2 with existing -data and a custom portal, a "Cannot convert null to primitive type org.chromattic.core.vt2.ValueDefinition" Null Pointer Exception was thrown at the second server startup. This fix upgrades the NewPortalConfigListener to correctly handle such data. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794437"> + <citetitle>BZ#794437</citetitle> + </ulink> - NullPointerException upgrading EPP from 5.1 to 5.2</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + After upgrading from EPP 5.1 to 5.2 with existing +data and a custom portal, a &quot;Cannot convert null to primitive type org.chromattic.core.vt2.ValueDefinition&quot; Null Pointer Exception was thrown at the second server startup. This fix upgrades the NewPortalConfigListener to correctly handle such data. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794331"><... - Text encoding is lost in serveResources</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794331"> + <citetitle>BZ#794331</citetitle> + </ulink> - Text encoding is lost in serveResources</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> It was discovered that when content was served from a portlet, the resource encoding was being rewritten with the default encoding of the running JVM. To work around the issue, users had to serve the resource as a binary, or set the system encoding to ISO-8859-1. The fix implements improved resource handling, which honors the mime type encoding when outputting byte array data. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794341"><... - imported gadgets can have more than max characters which causes problems</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - It was discovered that an imported remote gadget description could contain more than 255 characters. If a user tried to edit a gadget with more than 255 characters in the description, an error message displayed: <literal>"The length of the text in field "Description :" must be between "0" and "255" characters."</literal>. The fix allows gadgets to have an unrestricted description length, which fixes the originally reported issue. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794341"> + <citetitle>BZ#794341</citetitle> + </ulink> - imported gadgets can have more than max characters which causes problems</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + It was discovered that an imported remote gadget description could contain more than 255 characters. If a user tried to edit a gadget with more than 255 characters in the description, an error message displayed: <literal>&quot;The length of the text in field &quot;Description :&quot; must be between &quot;0&quot; and &quot;255&quot; characters.&quot;</literal>. The fix allows gadgets to have an unrestricted description length, which fixes the originally reported issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794349"><... - Application Registry has double entries for some applications</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - An issue with the 'Import Applications' request of the Application Registry caused some applications already added to a category to be added again. The fix implements logic changes to the 'Import Applications' request that check for already existing applications in a category. + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794349"> + <citetitle>BZ#794349</citetitle> + </ulink> - Application Registry has double entries for some applications</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + An issue with the &apos;Import Applications&apos; request of the Application Registry caused some applications already added to a category to be added again. The fix implements logic changes to the &apos;Import Applications&apos; request that check for already existing applications in a category. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794402"><... - Consistent initialization order of servlets/portlets at deploy and hot-deploy</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794402"> + <citetitle>BZ#794402</citetitle> + </ulink> - Consistent initialization order of servlets/portlets at deploy and hot-deploy</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> Spring-specific portlet and servlet initialization ordering requirements caused Spring-based portlets to work when the server was first started, but fail on hot deployment. The fix introduces updates to the WCI component that allow manual registration of web applications that use a servlet. By specifying the load-on-start values between the registration portlet and the spring portlet, the way a portlet is initialized in relation to a servlet can be controlled. This fix only controls when the web application is registered in WCI with regards to another servlet, and not the servlet ordering with respect to portlets. There are multiple steps which need to be manually configured. Refer to the Bugzilla directly for more information and links to setup information. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794357"><... - possible to clone or copy system nodes in edit navigation</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - An issue with node copy or clone behavior allowed users to copy or clone a system node but not delete the node. This was caused by the node already being a system node, and therefore could not be deleted based on context. This issue + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794357"> + <citetitle>BZ#794357</citetitle> + </ulink> - possible to clone or copy system nodes in edit navigation</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + An issue with node copy or clone behavior allowed users to copy or clone a system node but not delete the node. This was caused by the node already being a system node, and therefore could not be deleted based on context. This issue has been fixed and included in this release of the product. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794396"><... - Deleting created subnode populates NPE and parent node is not properly deleted</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794396"> + <citetitle>BZ#794396</citetitle> + </ulink> - Deleting created subnode populates NPE and parent node is not properly deleted</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> It was discovered that deleting a navigation sub-node in a transient state (added in the Edit Navigation screen, but not yet saved) caused a Null Pointer Exception (NPE) and the parent navigation node was not correctly deleted. The fix introduces changes to the Edit Navigation logic that ensures the parent-child node relationship is handled correctly when deleted. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793246"><... - Logo portlet on Dashboard - url validation</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - URLs provided to the logo portlets were improperly + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793246"> + <citetitle>BZ#793246</citetitle> + </ulink> - Logo portlet on Dashboard - url validation</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + URLs provided to the logo portlets were improperly validated, excluding absolute URLs when they should have been allowed. This caused an error with the default URL. The URL validation scheme has been modified to allow absolute URLs, which corrects the issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793701"><... - XSD NS references have bad URL in organization-configuration.xml</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - The XMLNS URLs in the <filename>02portal.war/WEB-INF/conf/organization/organization-configuration.xml</filename> file's NAMESPACE declaration contained an incorrect namespace URL. The fix corrects the issue for new installations. If you have created a custom server profile, ensure you manually change www.<replaceable>exoplaform</replaceable>.org to www.<replaceable>exoplatform</replaceable>.org in the + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793701"> + <citetitle>BZ#793701</citetitle> + </ulink> - XSD NS references have bad URL in organization-configuration.xml</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> + The XMLNS URLs in the <filename>02portal.war/WEB-INF/conf/organization/organization-configuration.xml</filename> file&apos;s NAMESPACE declaration contained an incorrect namespace URL. The fix corrects the issue for new installations. If you have created a custom server profile, ensure you manually change www.<replaceable>exoplaform</replaceable>.org to www.<replaceable>exoplatform</replaceable>.org in the NAMESPACE declaration of the file. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794319"><... - Upgrade openid4java to resolve CVE-2011-4314</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794319"> + <citetitle>BZ#794319</citetitle> + </ulink> - Upgrade openid4java to resolve CVE-2011-4314</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> It was found that the Attribute Exchange (AX) extension of OpenID4Java was not checking to ensure attributes were signed. If AX was being used to receive information that an application only trusts the identity provider to assert, a remote attacker could use this flaw to conduct man-in-the-middle attacks and compromise the integrity of the information via a specially-crafted request. By default, only the JBoss Seam openid example application uses OpenID4Java. (<ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=754386">CVE...>) </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794385"><... - Czech localization labels for navigation nodes are missing</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794385"> + <citetitle>BZ#794385</citetitle> + </ulink> - Czech localization labels for navigation nodes are missing</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> Root portal navigation nodes did not have access to localized menu content. If a user selected their local language from the available portal language selector, the portal language would default to English. The fix includes the missing localization files, which corrects the originally reported issue. </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793909"><... - PicketLink fails to match identity object type due to whitespaces in its DN</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793909"> + <citetitle>BZ#793909</citetitle> + </ulink> - PicketLink fails to match identity object type due to whitespaces in its DN</term> + <listitem> + <remark>Status: CLOSED</remark> + <para> An issue in PicketLink identity verification resulted in domain names containing spaces causing the following exception to be raised: <literal>Cannot recognize identity object type by its DN</literal>. The fix implements changes to LDAPIdentityStoreRepository comparison logic, which compares the LDAP domain name with the domain name containing spaces. The logic ignores spaces in the domain name and searches for an overall character match. Domains that have a character match pass validation, which corrects the originally reported issue. </para> - </listitem> -</varlistentry> - - </variablelist> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=810345"> + <citetitle>BZ#810345</citetitle> + </ulink> - one-off patch: File name is not displayed correctly if it contains Portuguese accent characters during uploading</term> + <listitem> + <remark>Status: ASSIGNED</remark> + <para> + It was discovered that an issue with exo.portal.component.web.server caused the names of uploaded files to display incorrectly if they contained Portuguese accent characters. The fix provides an updated version of exo.portal.component.web.server with improvements to special international character encoding. The originally reported issue is resolved as a result of these improvements. + </para> + </listitem> + </varlistentry> + </variablelist> </chapter>