Author: jaredmorgs Date: 2012-03-21 00:50:40 -0400 (Wed, 21 Mar 2012) New Revision: 8623 Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_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/known.xml epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml Log: second draft pushed to stage for 5.2.1 release Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml 2012-03-21 04:47:38 UTC (rev 8622) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml 2012-03-21 04:50:40 UTC (rev 8623) @@ -190,8 +190,14 @@ </listitem> </varlistentry> <varlistentry> + <term>Java Open Single Sign-on (JOSSO) </term> + <listitem> + <para>Packaging changes require different file paths for JOSSO. Refer to the Reference Guide &quot;Java Open Single Sign-On Project&quot; section for more information.</para> + </listitem> + </varlistentry> + <varlistentry> <term> - <remark>Shiny New Component Number 2</remark> + <remark>Shiny New Component Number 3</remark> </term> <listitem> <para><remark>Some info about the shiny new component </remark></para> 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 2012-03-21 04:47:38 UTC (rev 8622) +++ epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2012-03-21 04:50:40 UTC (rev 8623) @@ -9,7 +9,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.1</edition> - <pubsnumber>1</pubsnumber> + <pubsnumber>2</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 2012-03-21 04:47:38 UTC (rev 8622) +++ epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2012-03-21 04:50:40 UTC (rev 8623) @@ -8,6 +8,20 @@ <simpara> <revhistory> <revision> + <revnumber>5.2.1-2</revnumber> + <date>Wed Mar 21 2012</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email>jmorgan [at] redhat [dot] com</email> + </author> + <revdescription> + <simplelist> + <member>Second draft run of Release Notes doc using BZ extraction script for JBoss Enterprise Portal Platform 5.2.1 GA.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.1-1</revnumber> <date>Mon Mar 19 2012</date> <author> Modified: epp/docs/branches/5.2/Release_Notes/en-US/known.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-03-21 04:47:38 UTC (rev 8622) +++ epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-03-21 04:50:40 UTC (rev 8623) @@ -50,5 +50,14 @@ </listitem> </varlistentry> +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793804" /></term> + <listitem> + <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 is configurable from the organization-configuration.xml 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> + </variablelist> </chapter> Modified: epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml 2012-03-21 04:47:38 UTC (rev 8622) +++ epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml 2012-03-21 04:50:40 UTC (rev 8623) @@ -19,35 +19,16 @@ <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793639" /></term> <listitem> <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 JBOSS_HOME/server/[PROFILE]/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml, which imports the static configuration stored in the initializer-configuration.xml file . + 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 JBOSS_HOME/server/[PROFILE]/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml, 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" /></term> - <listitem> - <para> - CAUSE: when memberships of some user are changed (For example user root will remove user john from group /platform/users group), then user john won't see updates immediately. He needs to logout and login to see it. Example: -1) Start browser1, Go to http://localhost:8080/portal and login as john. User john is in group /platform/administrators by default, so he can see "Administrators" link in group menu, -2) Start browser2, Go to http://localhost:8080/portal and login as root. Go to OrganizationManagement and remove user john from /platform/administrators -3) Return to browser1 and refresh page. User john can still see "administrators" pages, which is a bug. -4) Logout and login again as john. Now "Administrators" are not longer visible. Bad is that john needs to logout and login, otherwise permissions for pages are not reflected. - -FIX: I added new listener "MembershipUpdateListener" into organization-configuration.xml file. This listener will update all memberships of logged user in ConversationRegistry, so that changes are immediately reflected in UI. - -RESULT: Changes are immediately reflected in UI. In previous example, user john won't see "Administrators" page in step 3, which is correct. - </para> - </listitem> -</varlistentry> - -<varlistentry> <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794235" /></term> <listitem> <para> - CAUSE: When user login, he can see his fullname in right top corner. This is his fullName according to format "firstName lastName" and it's hardcoded so that users can't use different format. It is also quite bad for some languages like Japanese, where is common to use opposite order as fullName. - -FIX: There is new field "Display Name" in UI in all screens where is possible to create or edit user. So user is able to fill his displayName and this displayName will be used in right top corner instead of fullName. DisplayName is not mandatory and when user is not using it, it fallback to fullName (old behaviour). This also ensure backward compatibility with older versions of EPP. Name of new attribute in Picketlink IDM database is "displayName" but as said before, attribute is not mandatory. + 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> @@ -56,15 +37,7 @@ <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793838" /></term> <listitem> <para> - Release notes docs status: Not Yet Documented - -Release notes: CAUSE: Previously it was possible to integrate EPP only with JOSSO 1.8.1 - -FIX: It's fixed in EPP SSO component, which has been updated in EPP to have the fix available. Now it's still possible to integrate with JOSSO 1.8.1 but also with newer versions like 1.8.2, 1.8.3, 1.8.4 and 1.8.5. - -There is changed JOSSO agent API between JOSSO versions 1.8.1 and 1.8.2, which means that we need to have slightly different packaging for JOSSO 1.8.1 and for JOSSO 1.8.2 and newer. - -It also affects documentation and related Docs issue is https://bugzilla.redhat.com/show_bug.cgi?id=794433 + 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. </para> </listitem> </varlistentry>