March 2013 - gatein-commits - Jboss List Archives

gatein SVN: r9199 - in epp/docs/branches/6.0: Development_Guide and 1 other directories.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2013-03-13 01:05:06 -0400 (Wed, 13 Mar 2013) New Revision: 9199 Added: epp/docs/branches/6.0/Development_Guide/ epp/docs/branches/6.0/Development_Guide/en-US/Developer_Guide.xml epp/docs/branches/6.0/Development_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Development_Guide/publican.cfg Removed: epp/docs/branches/6.0/Developer_Guide/ epp/docs/branches/6.0/Development_Guide/en-US/Developer_Guide.xml epp/docs/branches/6.0/Development_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Development_Guide/publican.cfg Log: Renaming Developer Guide to Development Guide to match the new naming scheme before migrating to git Deleted: epp/docs/branches/6.0/Development_Guide/en-US/Developer_Guide.xml =================================================================== --- epp/docs/branches/6.0/Developer_Guide/en-US/Developer_Guide.xml 2013-03-04 11:10:20 UTC (rev 9194) +++ epp/docs/branches/6.0/Development_Guide/en-US/Developer_Guide.xml 2013-03-13 05:05:06 UTC (rev 9199) @@ -1,46 +0,0 @@ -<?xml version='1.0' encoding='UTF-8'?> -<!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 "Developer_Guide.ent"> -%BOOK_ENTITIES; -]> -<book status="draft"> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Introduction/Introduction.xml" encoding="UTF-8"/> - <part> - <title>Architectural and Design Choices</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Architectural_Design_Choices/Architectural_Choices.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Architectural_Design_Choices/Design_Choices.xml" encoding="UTF-8"/> - </part> - <part> - <title>Portal Development</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portal_Development/Portal_Containers.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portal_Development/Visual_Identity.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portal_Development/Portal_Extension.xml" encoding="UTF-8"/> - </part> - <part> - <title>Application Development</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Application_Development/Gadget_Development.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Application_Development/Portlet_Development.xml" encoding="UTF-8"/> - </part> - <part> - <title>JavaScript Development</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/JavaScript_Modularity.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/JavaScript_in_JBoss_Portal_Platform.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Module_Scopes.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Portlet_Dynamic_Module.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Aliases.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Custom_Adapters.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Module_Resources.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Load_Groups.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Localization.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Scripts_In_JBoss_Portal_Platform.xml" encoding="UTF-8"/> - </part> - <part> - <title>JavaScript Code Examples</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Module_Cookbook.xml" encoding="UTF-8"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Script_Cookbook.xml" encoding="UTF-8"/> - </part> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="appendix-Quickstarts.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> -</book> Copied: epp/docs/branches/6.0/Development_Guide/en-US/Developer_Guide.xml (from rev 9198, epp/docs/branches/6.0/Developer_Guide/en-US/Developer_Guide.xml) =================================================================== --- epp/docs/branches/6.0/Development_Guide/en-US/Developer_Guide.xml (rev 0) +++ epp/docs/branches/6.0/Development_Guide/en-US/Developer_Guide.xml 2013-03-13 05:05:06 UTC (rev 9199) @@ -0,0 +1,46 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!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 "Developer_Guide.ent"> +%BOOK_ENTITIES; +]> +<book> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Introduction/Introduction.xml" encoding="UTF-8"/> + <part> + <title>Architectural and Design Choices</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Architectural_Design_Choices/Architectural_Choices.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Architectural_Design_Choices/Design_Choices.xml" encoding="UTF-8"/> + </part> + <part> + <title>Portal Development</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portal_Development/Portal_Containers.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portal_Development/Visual_Identity.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Portal_Development/Portal_Extension.xml" encoding="UTF-8"/> + </part> + <part> + <title>Application Development</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Application_Development/Gadget_Development.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Application_Development/Portlet_Development.xml" encoding="UTF-8"/> + </part> + <part> + <title>JavaScript Development</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/JavaScript_Modularity.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/JavaScript_in_JBoss_Portal_Platform.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Module_Scopes.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Portlet_Dynamic_Module.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Aliases.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Custom_Adapters.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Module_Resources.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Load_Groups.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Localization.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Scripts_In_JBoss_Portal_Platform.xml" encoding="UTF-8"/> + </part> + <part> + <title>JavaScript Code Examples</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Module_Cookbook.xml" encoding="UTF-8"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="JavaScript_Development/Script_Cookbook.xml" encoding="UTF-8"/> + </part> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="appendix-Quickstarts.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> +</book> Deleted: epp/docs/branches/6.0/Development_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml 2013-03-04 11:10:20 UTC (rev 9194) +++ epp/docs/branches/6.0/Development_Guide/en-US/Revision_History.xml 2013-03-13 05:05:06 UTC (rev 9199) @@ -1,238 +0,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" []> -<appendix id="appe-Developer_Guide-Revision_History"> - <title>Revision History</title> - <simpara> - <revhistory> - <revision> - <revnumber>6.0.0-21</revnumber> - <date>Mon Mar 04 2013</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Added Portlet develpment with Richfaces topic and incorporated Jared review remarks for Quickstarts</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-20</revnumber> - <date>Fri Feb 27 2013</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#912678, BZ#856447- Resolved</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-18</revnumber> - <date>Fri Feb 21 2013</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#912678: NEEDINFO - Incorporating SME feedback</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-17</revnumber> - <date>Fri Feb 15 2013</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Re-added 'Quickstarts' appendix to the book.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-15</revnumber> - <date>Thu Feb 14 2013</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Edited incorporated content in IV. JavaScript Development - from Portlet Dynamic Module towards the end of the JavaScript Development part.</member> - <member>I also reformatted code examples in the whole JavaScript Development part to have consistent indenting and syntax highlighting.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-14</revnumber> - <date>Wed Feb 6 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Incorporated changes for BZ#907305, and made changes required for Custom Sign In Page.</member> - <member>Added an "Introducing JBoss Portal Platform" section for review and comment by all team members.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-12</revnumber> - <date>Tue Feb 5 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Refactored the entire guide, including XML at the back-end SVN repo. Chunking at the part level will allow the developer content in the Reference Guide to be ported over easily, into the section in which it belongs.</member> - <member>Gave all sections logical IDREF info so the html-single links would make sense and be human-readable.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-11</revnumber> - <date>Mon Feb 4 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Changes incorporated for https://docs.jboss.org/author/display/GTNPORTAL35/Custom+Navigation+and+P... in <xref linkend="Custom_Navigation_And_Pages"/>. Heavy nesting in this section caused me to restructure some of the deeply nested sections into examples.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-10</revnumber> - <date>Fri Feb 1 2013</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Changes incorporated for https://docs.jboss.org/author/display/GTNPORTAL35/Appendix+-+Code+Example...</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-9</revnumber> - <date>Thu Jan 31 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Changes incorporated for https://docs.jboss.org/author/display/GTNPORTAL35/Custom+Internationaliza...</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-7</revnumber> - <date>Wed Jan 23 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#886376 - Updated all Book_Info.xml files with consistent subtitle. Rebuilt for review..</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-6</revnumber> - <date>Fri Jan 18 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Added all the raw changes from the Portal Extension section on Confluence.</member> - <member>Incorporated changes up to Rev 4 from https://docs.jboss.org/author/display/GTNPORTAL35/Custom+Groovy+Template+... </member> - <member>Incorporated changes up to Rev 4 from https://docs.jboss.org/author/display/GTNPORTAL35/Custom+Skin+for+a+Portlet with a question about how Quickstarts will be delivered.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-5</revnumber> - <date>Tue Oct 30 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Standardized subtitle across all books.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-4</revnumber> - <date>Thu Oct 25 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Restaged book under the new JBoss Portal Platform banner.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-3</revnumber> - <date>Fri Oct 19 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Fixed a minor typo in chapter 3.2.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-1</revnumber> - <date>Wed Oct 11 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Implemented changes required in BZ#813583.</member> - </simplelist> - </revdescription> - </revision> - </revhistory> - </simpara> -</appendix> Copied: epp/docs/branches/6.0/Development_Guide/en-US/Revision_History.xml (from rev 9198, epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml) =================================================================== --- epp/docs/branches/6.0/Development_Guide/en-US/Revision_History.xml (rev 0) +++ epp/docs/branches/6.0/Development_Guide/en-US/Revision_History.xml 2013-03-13 05:05:06 UTC (rev 9199) @@ -0,0 +1,37 @@ +<?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" []> +<appendix id="appe-Developer_Guide-Revision_History"> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>6.0.0-21</revnumber> + <date>Mon Mar 04 2013</date> + <author> + <firstname>Aakanksha</firstname> + <surname>Singh</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>Added Portlet develpment with Richfaces topic and incorporated Jared review remarks for Quickstarts</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>6.0.0-100</revnumber> + <date>Tue Mar 05 2013</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>Prepared for JBoss Portal Platform 6.0 GA.</member> + </simplelist> + </revdescription> + </revision> + </revhistory> + </simpara> +</appendix> Deleted: epp/docs/branches/6.0/Development_Guide/publican.cfg =================================================================== --- epp/docs/branches/6.0/Developer_Guide/publican.cfg 2013-03-04 11:10:20 UTC (rev 9194) +++ epp/docs/branches/6.0/Development_Guide/publican.cfg 2013-03-13 05:05:06 UTC (rev 9199) @@ -1,6 +0,0 @@ -xml_lang: "en-US" -brand: JBoss -debug: 1 -type: Book -git_branch: docs-rhel-6 -show_remarks: 1 Copied: epp/docs/branches/6.0/Development_Guide/publican.cfg (from rev 9198, epp/docs/branches/6.0/Developer_Guide/publican.cfg) =================================================================== --- epp/docs/branches/6.0/Development_Guide/publican.cfg (rev 0) +++ epp/docs/branches/6.0/Development_Guide/publican.cfg 2013-03-13 05:05:06 UTC (rev 9199) @@ -0,0 +1,6 @@ +xml_lang: "en-US" +brand: JBoss +debug: 1 +type: Book +git_branch: docs-rhel-6 +#show_remarks: 1

11 years, 1 month

1
0
0 / 0

gatein SVN: r9198 - in epp/docs/branches/6.0: Admin_Guide and 10 other directories.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2013-03-06 17:42:45 -0500 (Wed, 06 Mar 2013) New Revision: 9198 Removed: epp/docs/branches/6.0/Confluence_Source/ epp/docs/branches/6.0/Migration_Guide/ epp/docs/branches/6.0/PicketLink_IDM_Reference_Guide/ Modified: epp/docs/branches/6.0/Admin_Guide/en-US/Administration_Guide.xml epp/docs/branches/6.0/Admin_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Admin_Guide/publican.cfg epp/docs/branches/6.0/Developer_Guide/en-US/Developer_Guide.xml epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Developer_Guide/publican.cfg epp/docs/branches/6.0/Installation_Guide/DON'T_EDIT_THIS_SOURCE epp/docs/branches/6.0/Migration_Notes/en-US/Revision_History.xml epp/docs/branches/6.0/Reference_Guide/en-US/Reference_Guide.xml epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Reference_Guide/publican.cfg epp/docs/branches/6.0/Release_Notes/en-US/6.0.0_Release_Notes.xml epp/docs/branches/6.0/Release_Notes/en-US/Components.xml epp/docs/branches/6.0/Release_Notes/en-US/Introduction.xml epp/docs/branches/6.0/Release_Notes/en-US/Revision_History.xml epp/docs/branches/6.0/Release_Notes/en-US/Unsupported_Features.xml epp/docs/branches/6.0/User_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/User_Guide/en-US/User_Guide.xml epp/docs/branches/6.0/User_Guide/publican.cfg Log: Deleting old or obsolete guides in preparation for JPP 6.1 Modified: epp/docs/branches/6.0/Admin_Guide/en-US/Administration_Guide.xml =================================================================== --- epp/docs/branches/6.0/Admin_Guide/en-US/Administration_Guide.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Admin_Guide/en-US/Administration_Guide.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Administration_Guide.ent"> %BOOK_ENTITIES; ]> -<book status="draft"> +<book> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> <part> Modified: epp/docs/branches/6.0/Admin_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Admin_Guide/en-US/Revision_History.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Admin_Guide/en-US/Revision_History.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -8,132 +8,19 @@ <simpara> <revhistory> <revision> - <revnumber>6.0.0-9</revnumber> - <date>Mon Feb 25 2013</date> + <revnumber>6.0.0-100</revnumber> + <date>Tue Mar 05 2013</date> <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#911447: Minor corrections as per QE feedback.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-8</revnumber> - <date>Wed Feb 20 2013</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Incremented pubsnumber to have book re-Brew-ed.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-7</revnumber> - <date>Fri Feb 15 2013</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Review and editing prior to cover-to-cover review by QE.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-6</revnumber> - <date>Fri Jan 25 2013</date> - <author> <firstname>Jared</firstname> <surname>Morgan</surname> <email/> </author> <revdescription> <simplelist> - <member>BZ#856436 - Updated GateIn JON Plug-in screenshot.</member> + <member>Prepared for JBoss Portal Platform 6.0 GA.</member> </simplelist> </revdescription> </revision> - <revision> - <revnumber>6.0.0-5</revnumber> - <date>Wed Jan 23 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#886376 - Updated all Book_Info.xml files with consistent subtitle. Rebuilt for review..</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-4</revnumber> - <date>Fri Nov 16 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Fixed file paths in Command line section as per remarks in this section.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-3</revnumber> - <date>Wed Nov 14 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856436 - Updated Administration and Monitoring section to reflect the minor changes Nick Scavelli made in https://docs.jboss.org/author/display/GTNPORTAL35/Administration+and+Moni.... With the exception of the Installing RHQ, because that is community-specific. See the Installation Guide for changes to installing JON Plugin info.</member> - <member>BZ#794408 - Petr Penicka updated the Import and Export procedures, in both the 5.2 and 6.0 docs.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-2</revnumber> - <date>Tue Oct 30 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Standardized subtitle across all books.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-1</revnumber> - <date>Thu Oct 25 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Re-brewed guide for new product name change to JBoss Portal Platform.</member> - </simplelist> - </revdescription> - </revision> </revhistory> </simpara> </appendix> Modified: epp/docs/branches/6.0/Admin_Guide/publican.cfg =================================================================== --- epp/docs/branches/6.0/Admin_Guide/publican.cfg 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Admin_Guide/publican.cfg 2013-03-06 22:42:45 UTC (rev 9198) @@ -4,5 +4,5 @@ debug: 1 type: Book git_branch: docs-rhel-6 -show_remarks: 1 +#show_remarks: 1 Modified: epp/docs/branches/6.0/Developer_Guide/en-US/Developer_Guide.xml =================================================================== --- epp/docs/branches/6.0/Developer_Guide/en-US/Developer_Guide.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Developer_Guide/en-US/Developer_Guide.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Developer_Guide.ent"> %BOOK_ENTITIES; ]> -<book status="draft"> +<book> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Introduction/Introduction.xml" encoding="UTF-8"/> Modified: epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -19,220 +19,19 @@ </revdescription> </revision> <revision> - <revnumber>6.0.0-20</revnumber> - <date>Fri Feb 27 2013</date> + <revnumber>6.0.0-100</revnumber> + <date>Tue Mar 05 2013</date> <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#912678, BZ#856447- Resolved</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-18</revnumber> - <date>Fri Feb 21 2013</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#912678: NEEDINFO - Incorporating SME feedback</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-17</revnumber> - <date>Fri Feb 15 2013</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Re-added 'Quickstarts' appendix to the book.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-15</revnumber> - <date>Thu Feb 14 2013</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Edited incorporated content in IV. JavaScript Development - from Portlet Dynamic Module towards the end of the JavaScript Development part.</member> - <member>I also reformatted code examples in the whole JavaScript Development part to have consistent indenting and syntax highlighting.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-14</revnumber> - <date>Wed Feb 6 2013</date> - <author> <firstname>Jared</firstname> <surname>Morgan</surname> <email/> </author> <revdescription> <simplelist> - <member>Incorporated changes for BZ#907305, and made changes required for Custom Sign In Page.</member> - <member>Added an "Introducing JBoss Portal Platform" section for review and comment by all team members.</member> + <member>Prepared for JBoss Portal Platform 6.0 GA.</member> </simplelist> </revdescription> </revision> - <revision> - <revnumber>6.0.0-12</revnumber> - <date>Tue Feb 5 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Refactored the entire guide, including XML at the back-end SVN repo. Chunking at the part level will allow the developer content in the Reference Guide to be ported over easily, into the section in which it belongs.</member> - <member>Gave all sections logical IDREF info so the html-single links would make sense and be human-readable.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-11</revnumber> - <date>Mon Feb 4 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Changes incorporated for https://docs.jboss.org/author/display/GTNPORTAL35/Custom+Navigation+and+P... in <xref linkend="Custom_Navigation_And_Pages"/>. Heavy nesting in this section caused me to restructure some of the deeply nested sections into examples.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-10</revnumber> - <date>Fri Feb 1 2013</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Changes incorporated for https://docs.jboss.org/author/display/GTNPORTAL35/Appendix+-+Code+Example...</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-9</revnumber> - <date>Thu Jan 31 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Changes incorporated for https://docs.jboss.org/author/display/GTNPORTAL35/Custom+Internationaliza...</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-7</revnumber> - <date>Wed Jan 23 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#886376 - Updated all Book_Info.xml files with consistent subtitle. Rebuilt for review..</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-6</revnumber> - <date>Fri Jan 18 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Added all the raw changes from the Portal Extension section on Confluence.</member> - <member>Incorporated changes up to Rev 4 from https://docs.jboss.org/author/display/GTNPORTAL35/Custom+Groovy+Template+... </member> - <member>Incorporated changes up to Rev 4 from https://docs.jboss.org/author/display/GTNPORTAL35/Custom+Skin+for+a+Portlet with a question about how Quickstarts will be delivered.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-5</revnumber> - <date>Tue Oct 30 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Standardized subtitle across all books.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-4</revnumber> - <date>Thu Oct 25 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Restaged book under the new JBoss Portal Platform banner.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-3</revnumber> - <date>Fri Oct 19 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Fixed a minor typo in chapter 3.2.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-1</revnumber> - <date>Wed Oct 11 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Implemented changes required in BZ#813583.</member> - </simplelist> - </revdescription> - </revision> </revhistory> </simpara> </appendix> Modified: epp/docs/branches/6.0/Developer_Guide/publican.cfg =================================================================== --- epp/docs/branches/6.0/Developer_Guide/publican.cfg 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Developer_Guide/publican.cfg 2013-03-06 22:42:45 UTC (rev 9198) @@ -3,4 +3,4 @@ debug: 1 type: Book git_branch: docs-rhel-6 -show_remarks: 1 +#show_remarks: 1 Modified: epp/docs/branches/6.0/Installation_Guide/DON'T_EDIT_THIS_SOURCE =================================================================== --- epp/docs/branches/6.0/Installation_Guide/DON'T_EDIT_THIS_SOURCE 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Installation_Guide/DON'T_EDIT_THIS_SOURCE 2013-03-06 22:42:45 UTC (rev 9198) @@ -4,4 +4,7 @@ The topic ID you need to pull is: 11942 +The Revision_History.xml file is included to keep track of the document's revision history. Update this file each time +you build using CSP, and commit the changes to SVN for the next writer. + Refer to the CSProcessor User Guide on engineering.redhat.com/docs for more information. Modified: epp/docs/branches/6.0/Migration_Notes/en-US/Revision_History.xml =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Reference_Guide.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/Reference_Guide.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Reference_Guide.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<book status="draft"> +<book> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="modules/Introduction.xml"/> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -7,768 +7,20 @@ <title>Revision History</title> <simpara> <revhistory> - <revision> - <revnumber>6.0.0-55</revnumber> - <date>Mon Mar 4 2013</date> + <revision> + <revnumber>6.0.0-100</revnumber> + <date>Tue Mar 05 2013</date> <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#911516 - Incorporated new QE Review comments.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-54</revnumber> - <date>Mon Mar 4 2013</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#911516,856448,856430 - Incorporated new QE Review comments.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-53</revnumber> - <date>Wed Feb 27 2013</date> - <author> <firstname>Jared</firstname> <surname>Morgan</surname> <email/> </author> <revdescription> <simplelist> - <member>BZ#913291 - Reviewed and corrected incorrect file paths in this section. Ready for QA.</member> + <member>Prepared for JBoss Portal Platform 6.0 GA.</member> </simplelist> </revdescription> </revision> - <revision> - <revnumber>6.0.0-52</revnumber> - <date>Wed Feb 27 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#911516 - Incorporated all QE Review comments to date.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-51</revnumber> - <date>Tue Feb 26 2013</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Included updated image in "SAML2 Authentication Overview".</member> - <member>Added "Generate and configure your own keystore" section in Confluence</member> - <member>Merge 'JPP as SP' and 'PicketLink as IDP' procedures</member> - <member>Finished all feedback from BZ#856430 comments #21-26</member> - <member>Language and grammar edit.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-49</revnumber> - <date>Mon Feb 18 2013</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856450 - Incorporated comments 10 and 11 in the bug - edits of the JOSSO, CAS and clustered SSO sections.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-48</revnumber> - <date>Fri Feb 15 2013</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#907696- Upload Component section removed as per instruction from Michal Vanco.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-47</revnumber> - <date>Thu Feb 07 2013</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#886289- Incorporated review comments on OpenAM.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-46</revnumber> - <date>Fri Feb 05 2013</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#907672 - Incorporated "Upload Component" content from Confluence wiki, up to version 3.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-45</revnumber> - <date>Fri Feb 01 2013</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856450 - Implemented all JOSSO review comments from Tomas K. Ready for verification.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-44</revnumber> - <date>Wed Jan 30 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856450 - Implemented all CAS QE review comments from Tomas K. Ready for verification.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-43</revnumber> - <date>Wed Jan 30 2013</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Cleaned up imported content in Chapter III. - Authentication and Authorization.</member> - <member>Cleared out TODO, FIXME and some other remarks, further code cleanup, spell-check, unified capitals in titles, removed links to docs.jboss.org (where applicable), removed some technical jargon, etc.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-42</revnumber> - <date>Tue Jan 27 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>==Ready for Engineering Field Staff review==</member> - <member>Added notes from Marek concerning LDAP as a Default Store.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-41</revnumber> - <date>Tue Jan 27 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>==Ready for Engineering Field Staff review==</member> - <member>Incorporated feedback for BZ#903884 "Default Portal Configuration".</member> - <member>Changed all references to $JBOSS_HOME to JPP_HOME, and added this file path abbreviation to <xref linkend="sect-File_Name_Conventions"/>.</member> - <member>Reviewed all file path abbreviations, and remove the JBOSS_SERVER abbreviation, which was basically the same as JPP_HOME.</member> - <member>Added notes from Marek concerning LDAP as a Default Store.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-40</revnumber> - <date>Mon Jan 26 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Incorporated all feedback from Thomas from the Email review, except for some stuff from WSRP. See next entries.</member> - <member>WSRP review due to missing or incorrect file paths identified by Thomas in email review.</member> - <member>Added Confluence Source links to Securing WSRP.</member> - <member>Moved Server Integration chapter before the Revision History, so the Publican build would not break.</member> - <member>Removed all JBoss AS7, JBossAS 7, JBoss AS 7, GateIn Portal references.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-39</revnumber> - <date>Sat Jan 26 2013</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Updated chapters WSRP, added section Server Integration</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-38</revnumber> - <date>Fri Jan 25 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Sanitized all old file paths. NEEDINFO - FILE PATH used in remarks to flag areas where I need assistance with info for old file paths.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-37</revnumber> - <date>Fri Jan 25 2013</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#886298: Corrections as per feedback from Tomas.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-35</revnumber> - <date>Fri Jan 25 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Changes incorporated for https://docs.jboss.org/author/display/GTNPORTAL35/Default+Portal+Configur.... Ready for QE.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-34</revnumber> - <date>Fri Jan 25 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856453 - Incorporated all QE feedback from Tomas for LDAP. Ready for Verification.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-33</revnumber> - <date>Wed Jan 23 2013</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Rebased changes for https://docs.jboss.org/author/display/GTNPORTAL35/Portal+Navigation+Confi... </member> - <member>Rebased changes for https://docs.jboss.org/author/display/GTNPORTAL35/Working+with+WSRP+exten...</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-32</revnumber> - <date>Wed Jan 23 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#886376 - Updated all Book_Info.xml files with consistent subtitle. Rebuilt for review..</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-31</revnumber> - <date>Tue Jan 22 2013</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Imported raw content for chapters for Password Encryption and PicketLink IDM integration.</member> - <member>Rebased changes for https://docs.jboss.org/author/display/GTNPORTAL35/PicketLink+IDM+integration</member> - <member>Rebased changes for https://docs.jboss.org/author/display/GTNPORTAL35/Password+Encryption</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-30</revnumber> - <date>Thu Jan 17 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Final comments done for https://docs.jboss.org/author/display/GTNPORTAL35/Internationalization+Co.... Section ready for QA.</member> - <member>Rebased changes for https://docs.jboss.org/author/display/GTNPORTAL35/Configuring+GateIn%27s+...</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-29</revnumber> - <date>Wed Jan 16 2013</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Made changes from https://docs.jboss.org/author/display/GTNPORTAL35/Internationalization+Co... </member> - <member>I have some NEEDINFO to be answered by ppalaga before this can be finalized.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-28</revnumber> - <date>Mon Jan 7 2013</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#886289 and BZ#886298 - Implemented changes requested by SME review. The OpenAM and SPNEGO docs are now ready for docs QA.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-27</revnumber> - <date>Fri Jan 4 2013</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#886289 and BZ#886298 - Final version of OpenAM and SPNEGO single sign-on docs as submitted for SME review. Bonus: cleaned up File Name Conventions in Preface - removed unused abbreviations and made the descriptions more accurate.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-26</revnumber> - <date>Mon Dec 21 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#886289 and BZ#886298 - Updated sections on OpenAM and SPNEGO single sign-on. 99% ready, minor details regarding OpenAM packaging need to be clarified with SMEs, these are marked with TODO-prefixed comments in the XML source.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-19</revnumber> - <date>Mon Dec 12 2012</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856432 - Added WSRP content related to CXF and WS-Security from https://docs.jboss.org/author/display/GTNPORTAL35/Securing+WSRP</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-18</revnumber> - <date>Mon Dec 11 2012</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856445 - Removed instances of unsupported version of desktop browsers </member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-24</revnumber> - <date>Tue Dec 04 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856430 - Incorporated final changes by Marek for CAS. These changes are considered final, and ready for release.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-23</revnumber> - <date>Fri Nov 30 2012</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#807499: Added SME approved content regarding advanced WCI registration features.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-22</revnumber> - <date>Fri Nov 30 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856430 - Incorporated changes suggested by Marek to the CAS section.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-21</revnumber> - <date>Thu Nov 29 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856453 - Made the minor, required changes to the LDAP section as identified by Marek in the BS issue.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-20</revnumber> - <date>Wed Nov 28 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856430 - Rebased the CAS section from the work done by Marek at https://docs.jboss.org/author/display/GTNPORTAL35/Central+Authentication+... </member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-18</revnumber> - <date>Thu Nov 15 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#876821 - Removed obsolete chapters and sections from the JCR part, according to the guidance in the ticket. </member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-17</revnumber> - <date>Mon Nov 5 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856417 - Added Examples to Portlet Bridge section from content in https://docs.jboss.org/author/display/PBR/Examples, and did a final review of content before submitting JSF2 and RF4 tasks for QE validation. </member> - <member>Also removed text references to JBoss Enterprise Portal Platform, Enterprise Portal Platform, JPP_HOME, and JPP_DIST.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-16</revnumber> - <date>Fri Nov 02 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#794099 - added info about creation of custom error pages.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-15</revnumber> - <date>Thu Nov 01 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856427 - Added Implementing Portlet Bridge section from content contained at https://docs.jboss.org/author/display/PBR/Installing+Portlet+Bridge</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-14</revnumber> - <date>Thu Nov 01 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#850885 - added relevant information about rendering of route parameters.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-13</revnumber> - <date>Tue Oct 30 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Put in idrefs for all SAML 2 content, and changed title of subtitle for uniformity.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-12</revnumber> - <date>Mon Oct 25 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Restaging book under the JBoss Portal Platform name.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-11</revnumber> - <date>Mon Oct 24 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856430 - Updated the Central Authentication Storage (CAS) section with info from the .txt file. Lots of NEEDINFO in this update, but hopefully the changes will give Marek a base to work from when he looks at providing updates to the docs formally.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-10</revnumber> - <date>Tue Oct 23 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#803781 - removed mention of MyISAM engine.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-9</revnumber> - <date>Mon Oct 23 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856430 - Added SAML2 information received from Marek to the guide, and will await further information regarding generating keystores for use in production environments.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-8</revnumber> - <date>Mon Oct 22 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Replaced callouts in all code examples with code comments.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-7</revnumber> - <date>Fri Oct 22 2012</date> - <author> - <firstname>Eva</firstname> - <surname>Kopalova</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Bug 850746 - Remove Chapter 41. eXo JCR Backup Service and Chapter 42. HTTPBackupAgent and Backup Client from JPP Reference Guide.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-6</revnumber> - <date>Fri Oct 19 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#851691 - fixed broken lines in code examples caused by callouts throughout the whole guide. Issue with image links not resolved due to Publican 3.0 bug.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-5</revnumber> - <date>Thu Oct 18 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#851691 - updated supported DBs, LDAP servers, + minor issues. Issue with image links not resolved due to Publican 3.0 bug.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-4</revnumber> - <date>Mon Oct 15 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Implemented changes required in BZ#855858.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-3</revnumber> - <date>Fri Oct 12 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#865640 - Amended the JOSSO wording to clarify that Red Hat does not support JOSSO server, but offers integration with the server. </member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-2</revnumber> - <date>Wed Oct 3 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856417 - Comments incorporated from Ken Finnegan. NEEDINFO stated in remarks in section. Search for the BZ number to find instances requiring review. </member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-1</revnumber> - <date>Mon Sep 24 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856417 - First draft containing Portlet Bridge work. </member> - </simplelist> - </revdescription> - </revision> </revhistory> </simpara> </appendix> Modified: epp/docs/branches/6.0/Reference_Guide/publican.cfg =================================================================== --- epp/docs/branches/6.0/Reference_Guide/publican.cfg 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Reference_Guide/publican.cfg 2013-03-06 22:42:45 UTC (rev 9198) @@ -3,4 +3,4 @@ debug: 1 type: Book git_branch: docs-rhel-6 -show_remarks: 1 +#show_remarks: 1 Modified: epp/docs/branches/6.0/Release_Notes/en-US/6.0.0_Release_Notes.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/6.0.0_Release_Notes.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Release_Notes/en-US/6.0.0_Release_Notes.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -32,15 +32,88 @@ </listitem> </varlistentry> <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=902363">902363</ulink> - Invalid property 'PortalPermissionSelector' or 'PagePermissionSelector' instead of 'Access Permission Setting' </term> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=881812">881812</ulink> - WSRP - deregistered consumer is registered on reload (without refresh/register) </term> <listitem> <para> -An issue with missing i18n keys caused the PortalPermissionSelector and PagePermissionSelector i18n to be included instead of the translated UI text. Additionally, the icon was missing from the left of the translated string. The fix adds the two missing i18n keys using the #{UITabPane.title.UIListPermissionSelector} expression so that it was enough to add them into the file for locale 'en'. The .UITabSelector .FlatTabStyle .UIPermissionSelector24x24Icon rule was copied and renamed to match the expected class names PortalPermissionSelector24x24Icon and PagePermissionSelector24x24Icon. The forms now show internationalized texts and icons. +Previous versions of WSRP required consumers to be independently registered. WSRP Consumers are now automatically registered if the proper registration data is available when they are reloaded from the WSRP administration interface. </para> </listitem> </varlistentry> </variablelist> </section> + <section> + <title>Known Issues</title> + <variablelist> + <title>Portal</title> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=873733">873733</ulink> - WSRP - portlet import doesn't work </term> + <listitem> + <para> +Due to an issue with portal data caching on the consumer side, the portlet present before a WSRP import might still be visible after the import, when it should have changed. To work around the issue, users may need to log out and log back into the portal to see changes made after a WSRP portlet import. +</para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=917069">917069</ulink> - Unable to DnD gadgets on dashboard </term> + <listitem> + <para> +When you add any gadget to a dashboard portlet, it is not currently possible to drag-and-drop the gadget to a different position. To work around the issue, remove the gadget then re-add the gadget at the desired position. +</para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=877960">877960</ulink> - JSF2 portlet doesn't work over WSRP </term> + <listitem> + <para> +Because of poor resource support in WSRP v1, Java Server Faces (JSF) 2 can not properly transfer its required assets over WSRP. Subsequently, JSF 2 portlets are supported over WSRP v2 only. Customers should upgrade to WSRP v2, and phase-out WSRP v1 dependence in their production environment. +</para> + </listitem> + </varlistentry> + </variablelist> + <variablelist> + <title>PicketLink</title> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=915766">915766</ulink> - OrganizationService.getUserHandler().findUsersByGroupId(groupid) not working with H2 database </term> + <listitem> + <para> +The OrganizationService.getUserHandler().findUsersByGroupId(groupid) call does not work with the default Hypersonic 2 database. The call functions correctly with officially tested and supported databases. For a list of certified databases, refer to the Tested Configurations section of these release notes. +</para> + </listitem> + </varlistentry> + </variablelist> + <variablelist> + <title>Portal Packaging</title> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=905526">905526</ulink> - Swap files are not deleted with disabled value storage </term> + <listitem> + <para> +Content Repository API for Java (JCR) swap files are not deleted automatically. In extreme situations this issue could lead to server storage reaching capacity. To work around the issue, it is recommended to delete the +<code>JPP_HOME/standalone/data/gatein/jcr/swap/</code> +directory during maintenance procedures and before restarting the portal. +</para> + </listitem> + </varlistentry> + </variablelist> + <variablelist> + <title>PortletBridge</title> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=910308">910308</ulink> - Memory leak for RequestScoped, SessionScoped, and ViewScoped managed-beans </term> + <listitem> + <para> +A bug in the Java Server Faces (JSF) implementation can lead to to a memory leak for RequestScoped, SessionScoped and ViewScoped managed-beans. There is no workaround for this issue. +</para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=903654">903654</ulink> - a4j:attachQueue still has same delay regardless on the requestDelay value </term> + <listitem> + <para> +The requestDelay value of a4j:attachQueue does not alter the delay value. A fix will be brought in from portlet bridge to fix the issue in a subsequent release. There is currently no workaround to this issue. +</para> + </listitem> + </varlistentry> + </variablelist> + </section> </chapter> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> </book> Modified: epp/docs/branches/6.0/Release_Notes/en-US/Components.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/Components.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Release_Notes/en-US/Components.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -3,7 +3,7 @@ ]> <chapter id="components"> <title>Components</title> - <para>The full list of component versions used in JBoss Portal Platform 6 is available at <ulink url="https://access.redhat.com/knowledge/node/119873/"/></para> + <para>The full list of component versions used in JBoss Portal Platform 6 is available at <ulink url="https://access.redhat.com/knowledge/articles/119873"/></para>  <member>Third draft of release notes for JBoss Portal Platform 6.0.0 Beta</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-4</revnumber> - <date>Mon Dec 17 2012</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Second draft of release notes for JBoss Portal Platform 6.0.0 Beta</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-3</revnumber> - <date>Fri Dec 14 2012</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Edits for release notes for JBoss Portal Platform 6.0.0 Beta</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-2</revnumber> - <date>Thu Dec 13 2012</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Edits for release notes for JBoss Portal Platform 6.0.0 Beta</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-1</revnumber> - <date>Fri Dec 7 2012</date> - <author> - <firstname>Russell</firstname> - <surname>Dickenson</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>First Draft Release Notes prepared for JBoss Enterprise Portal Platform 6.0.0 Beta.</member> - </simplelist> - </revdescription> - </revision> </revhistory> </simpara> </appendix> Modified: epp/docs/branches/6.0/Release_Notes/en-US/Unsupported_Features.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/Unsupported_Features.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/Release_Notes/en-US/Unsupported_Features.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -4,6 +4,5 @@ <chapter id="usupported_features"> <title>Unsupported Features</title> <para>Site Publisher add-on is not available with JBoss Portal Platform 6.0.0 and future versions.</para> - <remark>BZ#892784 - jmorgan - made mention that domain mode is not supported for JPP 6.</remark> <para>The Domain server profile present in JBoss Enterprise Application Platform 6 is not supported in JBoss Portal Platform 6. Standalone mode is the correct profile to use for all portal platform servers.</para> </chapter> Modified: epp/docs/branches/6.0/User_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/User_Guide/en-US/Revision_History.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/User_Guide/en-US/Revision_History.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -8,145 +8,19 @@ <simpara> <revhistory> <revision> - <revnumber>6.0.0-14</revnumber> - <date>Wed Feb 27 2013</date> + <revnumber>6.0.0-100</revnumber> + <date>Tue Mar 05 2013</date> <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856442: Updated screenshots for new product name and skin colors.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-11</revnumber> - <date>Wed Feb 20 2013</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856445 - Updated topic supported browsers</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-10</revnumber> - <date>Wed Jan 23 2013</date> - <author> <firstname>Jared</firstname> <surname>Morgan</surname> <email/> </author> <revdescription> <simplelist> - <member>BZ#886376 - Updated all Book_Info.xml files with consistent subtitle. Rebuilt for review..</member> + <member>Prepared for JBoss Portal Platform 6.0 GA.</member> </simplelist> </revdescription> </revision> - <revision> - <revnumber>6.0.0-9</revnumber> - <date>Mon Dec 06 2012</date> - <author> - <firstname>Aakanksha</firstname> - <surname>Singh</surname> - <email>aasingh(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>BZ#856445 - removed references to unsupported version of browser.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-8</revnumber> - <date>Mon Nov 12 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Minor edits of work done in BZ#813776.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-7</revnumber> - <date>Mon Nov 8 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#813776 - removed various screenshots with no added information value and fixed various minor errors identified by docs QE.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-6</revnumber> - <date>Tue Oct 30 2012</date> - <author> - <firstname>Jared</firstname> - <surname>Morgan</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Rebuilt book so it would appear under the JBoss Portal Platform banner, and standardized subtitle across all books.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-4</revnumber> - <date>Wed Oct 17 2012</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>BZ#856442: Removed numerous unnecessary images.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-3</revnumber> - <date>Wed Oct 10 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Implemented changes required in BZ#849806.</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>6.0.0-2</revnumber> - <date>Fri Sep 12 2012</date> - <author> - <firstname>Petr</firstname> - <surname>Penicka</surname> - <email/> - </author> - <revdescription> - <simplelist> - <member>Implemented changes required in BZ#794408.</member> - </simplelist> - </revdescription> - </revision> </revhistory> </simpara> </appendix> Modified: epp/docs/branches/6.0/User_Guide/en-US/User_Guide.xml =================================================================== --- epp/docs/branches/6.0/User_Guide/en-US/User_Guide.xml 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/User_Guide/en-US/User_Guide.xml 2013-03-06 22:42:45 UTC (rev 9198) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "User_Guide.ent"> %BOOK_ENTITIES; ]> -<book status="draft"> +<book> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Preface.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="modules/Introduction.xml"/> Modified: epp/docs/branches/6.0/User_Guide/publican.cfg =================================================================== --- epp/docs/branches/6.0/User_Guide/publican.cfg 2013-03-06 04:07:53 UTC (rev 9197) +++ epp/docs/branches/6.0/User_Guide/publican.cfg 2013-03-06 22:42:45 UTC (rev 9198) @@ -3,5 +3,5 @@ debug: 1 type: Book git_branch: docs-rhel-6 -show_remarks: 1 +#show_remarks: 1

11 years, 1 month

1
0
0 / 0

gatein SVN: r9197 - epp/docs/branches/6.0/Installation_Guide.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2013-03-05 23:07:53 -0500 (Tue, 05 Mar 2013) New Revision: 9197 Removed: epp/docs/branches/6.0/Installation_Guide/en-US/ epp/docs/branches/6.0/Installation_Guide/pom.xml epp/docs/branches/6.0/Installation_Guide/publican.cfg Log: Removing all committed files from the Installation Guide directory so there is no confusion about content source Deleted: epp/docs/branches/6.0/Installation_Guide/pom.xml =================================================================== --- epp/docs/branches/6.0/Installation_Guide/pom.xml 2013-03-06 03:27:32 UTC (rev 9196) +++ epp/docs/branches/6.0/Installation_Guide/pom.xml 2013-03-06 04:07:53 UTC (rev 9197) @@ -1,216 +0,0 @@ -<project xmlns="http://maven.apache.org/POM/4.0.0" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> - - <modelVersion>4.0.0</modelVersion> - <groupId>org.gatein.docs.dummy</groupId> - <artifactId>${docname}-${translation}</artifactId> - <version>1.0-SNAPSHOT</version> - <packaging>jdocbook</packaging> - <name>${bookname}-(${translation})</name> - - <properties> - <translation>en-US</translation> - <docname>Installation_Guide</docname> - <bookname>Installation Guide</bookname> - </properties> - - <repositories> - <repository> - <id>repository.jboss.org</id> - <name>JBoss Repository</name> - <layout>default</layout> - <url>http://repository.jboss.org/maven2/</url> - <snapshots> - <enabled>false</enabled> - </snapshots> - </repository> - </repositories> - <pluginRepositories> - <pluginRepository> - <id>repository.jboss.org</id> - <name>JBoss Repository</name> - <layout>default</layout> - <url>http://repository.jboss.org/maven2/</url> - <snapshots> - <enabled>false</enabled> - </snapshots> - </pluginRepository> - </pluginRepositories> - - - <profiles> - -  - <profile> - <id>all</id> - <activation> - <activeByDefault>true</activeByDefault> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.2.0</version> - <extensions>true</extensions> - <configuration> - <formats> - <format> - <formatName>pdf</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource> - <finalName>${docname}.pdf</finalName> - </format> - <format> - <formatName>html</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - <format> - <formatName>html_single</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - </formats> - </configuration> - </plugin> - </plugins> - </build> - </profile> - -  - <profile> - <id>html</id> - <activation> - <activeByDefault>false</activeByDefault> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.2.0</version> - <extensions>true</extensions> - <configuration> - <formats> - <format> - <formatName>html</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - </formats> - </configuration> - </plugin> - </plugins> - </build> - </profile> - -  - <profile> - <id>html-single</id> - <activation> - <activeByDefault>false</activeByDefault> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.2.0</version> - <extensions>true</extensions> - <configuration> - <formats> - <format> - <formatName>html_single</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - </formats> - </configuration> - </plugin> - </plugins> - </build> - </profile> - -  - <profile> - <id>pdf</id> - <activation> - <activeByDefault>false</activeByDefault> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.2.0</version> - <extensions>true</extensions> - <configuration> - <formats> - <format> - <formatName>pdf</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource> - <finalName>${docname}.pdf</finalName> - </format> - </formats> - </configuration> - </plugin> - </plugins> - </build> - </profile> - - </profiles> - - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.2.0</version> - <extensions>true</extensions> - <dependencies> - <dependency> - <groupId>org.jboss</groupId> - <artifactId>jbossorg-docbook-xslt</artifactId> - <version>1.1.0</version> - </dependency> - <dependency> - <groupId>org.jboss</groupId> - <artifactId>jbossorg-jdocbook-style</artifactId> - <version>1.1.0</version> - <type>jdocbook-style</type> - </dependency> - </dependencies> - <configuration> - <sourceDocumentName>${docname}.xml</sourceDocumentName> - <sourceDirectory>.</sourceDirectory> - <imageResource> - <directory>${translation}</directory> - <includes> - <include>images/*</include> - </includes> - </imageResource> - <options> - <xincludeSupported>true</xincludeSupported> - <xmlTransformerType>saxon</xmlTransformerType> -  -  - <docbookVersion>1.72.0</docbookVersion> - <transformerParameters> - <property> - <name>javax.xml.parsers.DocumentBuilderFactory</name> - <value>org.apache.xerces.jaxp.DocumentBuilderFactoryImpl</value> - </property> - <property> - <name>javax.xml.parsers.SAXParserFactory</name> - <value>org.apache.xerces.jaxp.SAXParserFactoryImpl</value> - </property> - </transformerParameters> - </options> - </configuration> - </plugin> - - </plugins> - </build> - -</project> Deleted: epp/docs/branches/6.0/Installation_Guide/publican.cfg =================================================================== --- epp/docs/branches/6.0/Installation_Guide/publican.cfg 2013-03-06 03:27:32 UTC (rev 9196) +++ epp/docs/branches/6.0/Installation_Guide/publican.cfg 2013-03-06 04:07:53 UTC (rev 9197) @@ -1,6 +0,0 @@ -xml_lang: en-US -type: Book -brand: JBoss -debug:1 -#show_remarks:1 -git_branch: docs-rhel-6

11 years, 2 months

1
0
0 / 0

gatein SVN: r9196 - epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity.

by do-not-reply＠jboss.org

Author: smumford Date: 2013-03-05 22:27:32 -0500 (Tue, 05 Mar 2013) New Revision: 9196 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml Log: BZ#911516: Committing comment 16 changes Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-03-06 01:20:50 UTC (rev 9195) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-03-06 03:27:32 UTC (rev 9196) @@ -51,23 +51,20 @@ </para> <para>In <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename>, authentication is triggered by accessing a secured URL <systemitem>/dologin</systemitem>: </para> - <programlisting language="XML"> -<security-constraint> - <web-resource-collection> - <web-resource-name>user authentication</web-resource-name> - <url-pattern>/dologin</url-pattern> - <http-method>POST</http-method> - <http-method>GET</http-method> - </web-resource-collection> - <auth-constraint> - <role-name>users</role-name> - </auth-constraint> - <user-data-constraint> - <transport-guarantee>NONE</transport-guarantee> - </user-data-constraint> - </web-resource-collection> -</security-constraint> -</programlisting> + <programlisting language="XML"><![CDATA[<security-constraint> + <web-resource-collection> + <web-resource-name>user authentication</web-resource-name> + <url-pattern>/dologin</url-pattern> + <http-method>POST</http-method> + <http-method>GET</http-method> + </web-resource-collection> + <auth-constraint> + <role-name>users</role-name> + </auth-constraint> + <user-data-constraint> + <transport-guarantee>NONE</transport-guarantee> + </user-data-constraint> +</security-constraint>]]></programlisting> <para> This means that access to URLs (such as <ulink url="http://localhost:8080/portal/dologin" type="http">http://localhost:8080/portal/dologin</ulink>) will directly trigger J2EE authentication in the case that the user is not already logged in. </para> @@ -105,9 +102,6 @@ <para> After a user submits the login form, the LoginServlet will store credentials and trigger WCI login, which delegates to Servlet API (method HttpServletRequest.login(String username, String password) available in Servlet 3.0) and additionally triggers WCI Authentication listeners. Login through Servlet API delegates to JAAS. </para> - <para> - This URL is mapped to <literal>LoginServlet</literal> servlet, which stores credentials and redirects again to <literal>LoginServlet</literal>. LoginServlet triggers WCI login, which delegates to Servlet API (method HttpServletRequest.login(String username, String password) available in Servlet 3.0) and additionally triggers WCI Authentication listeners. Login through Servlet API delegates to JAAS. - </para> </section> <section id="sect-Authentication_Authorization_Intro-Login_Modules"> <title>Login Modules</title> @@ -159,8 +153,8 @@ <term>JBossAS7LoginModule</term> <listitem> <para> - The most important login module, which is normally used to perform the whole authentication by itself. First it checks if an Identity object has been already created and saved into the sharedState map by previous login modules (like SSODelegateLoginModule, CustomMembershipLoginModule or SharedStateLoginModule). If not, it triggers real authentication of the user with usage of the Authenticator interface and it will use <filename>Authentication.validateUser(Credential[] credentials)</filename> which performs real authentication of username and password against OrganizationService and the portal identity database. See <xref linkend="sect-Authentication_Authorization_Intro-authenticatorAndRolesExtractor"/> for details about Authenticator and about Identity objects. </para> - <para>In the <filename>JBossAS7LoginModule.commit</filename> method, the Identity object is registered to IdentityRegistry, which will be used later for authorization. Also some JAAS principals (UserPrincipal and RolesPrincipal) are assigned to our authenticated Subject. This is needed for JBoss Enterprise Application server, so that it can properly recognize the name of the logged user and its roles on an application server level. + The most important login module, which is normally used to perform the whole authentication by itself. First it checks if an Identity object has been already created and saved into the sharedState map by previous login modules (like SSODelegateLoginModule, CustomMembershipLoginModule or SharedStateLoginModule). If not, it triggers real authentication of the user with usage of the Authenticator interface and it will use <literal>Authentication.validateUser(Credential[] credentials)</literal> which performs real authentication of username and password against OrganizationService and the portal identity database. See <xref linkend="sect-Authentication_Authorization_Intro-authenticatorAndRolesExtractor"/> for details about Authenticator and about Identity objects. </para> + <para>In the <literal>JBossAS7LoginModule.commit</literal> method, the Identity object is registered to IdentityRegistry, which will be used later for authorization. Also some JAAS principals (UserPrincipal and RolesPrincipal) are assigned to our authenticated Subject. This is needed for JBoss Enterprise Application server, so that it can properly recognize the name of the logged user and its roles on an application server level. </para> </listitem> </varlistentry> @@ -176,7 +170,7 @@ Special login module, which can be used to add a user to existing groups during a successful login of this user. The group name is configurable and by default is /platform/users group. This login module is not used because in normal environment, users are already in the /platform/users group. It is useful only for some special setups like read-only LDAP, where groups of an LDAP user are taken from the LDAP tree so that users may not be in the /platform/users group, which is needed for successful authorization. </para> <para> - Note that the CustomMembershipLoginModule cannot be the first login module in the LoginModule chain because it assumes that the Identity object is already available in the shared state. So there are two possible cases. For a non-SSO case, you may need to chain this login module with other login modules, which can be used to establish Identity and add it into shared state. Those login modules can be <filename>InitSharedStateLoginModule</filename> and <filename>SharedStateLoginModule</filename>. For an SSO case, you can add <filename>CustomMembershipLoginModule</filename> between <filename>SSODelegateLoginModule</filename> and JBossAS7LoginModule. + Note that the CustomMembershipLoginModule cannot be the first login module in the LoginModule chain because it assumes that the Identity object is already available in the shared state. So there are two possible cases. For a non-SSO case, you may need to chain this login module with other login modules, which can be used to establish Identity and add it into shared state. Those login modules can be <literal>InitSharedStateLoginModule</literal> and <literal>SharedStateLoginModule</literal>. For an SSO case, you can add <literal>CustomMembershipLoginModule</literal> between <literal>SSODelegateLoginModule</literal> and <literal>JBossAS7LoginModule</literal>. </para> </listitem> </varlistentry> @@ -399,7 +393,7 @@ </listitem> <listitem> <para> - A HTTP request such as <ulink url="http://localhost:8080/portal/login?initialURI=/portal/classic&amp;use..."/> is sent to the server. This is not a HTTP GET request and the parameters are not encoded in the URL. The login form is submitted in a HTTP POST request to the /portal/login URL. + Form data such as <literal>username</literal>, <literal>password</literal> and <literal>rememberme</literal> are sent in an HTTP POST request to the <uri>/portal/login</uri> URL, with the <literal>rememberme</literal> parameter set to true. </para> </listitem> <listitem> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml 2013-03-06 01:20:50 UTC (rev 9195) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml 2013-03-06 03:27:32 UTC (rev 9196) @@ -82,7 +82,7 @@ </programlisting> </informalexample> <para> - Please note that specified file <code>/salt/mysalt.txt</code> must exist and must be readable by user, which executed JBoss Portal Platform. The file should be properly secured so that it is not readable by every user of your operating syste,. The content of the file can be a random phrase, such as: <emphasis role="italics">a4564dac2aasddsklklkajdgnioiow</emphasis>. + Please note that specified file <code>/salt/mysalt.txt</code> must exist and must be readable by user, which executed JBoss Portal Platform. The file should be properly secured so that it is not readable by every user of your operating system. The content of the file can be a random phrase, such as: <emphasis role="italics">a4564dac2aasddsklklkajdgnioiow</emphasis>. </para> <para> The <code>FileReadingSaltEncoder</code>is probably the most secure of all options, but in addition to <code>DatabaseReadingSaltEncoder</code>, you need to set the file with salt.

11 years, 2 months

1
0
0 / 0

gatein SVN: r9195 - epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity.

by do-not-reply＠jboss.org

Author: smumford Date: 2013-03-05 20:20:50 -0500 (Tue, 05 Mar 2013) New Revision: 9195 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SAML2.xml Log: BZ#856430: Committing comment 33 changes Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SAML2.xml =================================================================== (Binary files differ)

11 years, 2 months

1
0
0 / 0

gatein SVN: r9194 - in epp/docs/branches/6.0/Developer_Guide/en-US: Application_Development and 1 other directory.

by do-not-reply＠jboss.org

Author: aakanksha_writer Date: 2013-03-04 06:10:20 -0500 (Mon, 04 Mar 2013) New Revision: 9194 Modified: epp/docs/branches/6.0/Developer_Guide/en-US/Application_Development/Portlet_Development.xml epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Developer_Guide/en-US/appendix-Quickstarts.xml Log: richfaces Modified: epp/docs/branches/6.0/Developer_Guide/en-US/Application_Development/Portlet_Development.xml =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml 2013-03-04 03:54:54 UTC (rev 9193) +++ epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml 2013-03-04 11:10:20 UTC (rev 9194) @@ -4,6 +4,20 @@ <title>Revision History</title> <simpara> <revhistory> + <revision> + <revnumber>6.0.0-21</revnumber> + <date>Mon Mar 04 2013</date> + <author> + <firstname>Aakanksha</firstname> + <surname>Singh</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>Added Portlet develpment with Richfaces topic and incorporated Jared review remarks for Quickstarts</member> + </simplelist> + </revdescription> + </revision> <revision> <revnumber>6.0.0-20</revnumber> <date>Fri Feb 27 2013</date> Modified: epp/docs/branches/6.0/Developer_Guide/en-US/appendix-Quickstarts.xml =================================================================== --- epp/docs/branches/6.0/Developer_Guide/en-US/appendix-Quickstarts.xml 2013-03-04 03:54:54 UTC (rev 9193) +++ epp/docs/branches/6.0/Developer_Guide/en-US/appendix-Quickstarts.xml 2013-03-04 11:10:20 UTC (rev 9194) @@ -6,9 +6,8 @@ <para>The Quickstarts can be obtained in one of the following ways:</para> <section id="JBoss_Portal_Platform_Downloads_Page"> <title>JBoss Portal Platform Downloads Page</title> - <remark>Aakanksha, this was an itemized list for some reason. Not sure why, when it could just be a normal para. I have also made the URL visible, as per the standard for URLs. We shouldn't hide them for accessibility reasons. Also, we are supposed to use "see" instead of "refer to" (this is a recent thing introduced by ecs-standards@, of which you should be subscribed to).</remark> <para> - A zip archive containing all Quickstarts can be downloaded from the JBoss Portal Platform Downloads page, located at <ulink url="https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl..."/>.</para> +A zip archive containing all Quickstarts can be downloaded from the JBoss Portal Platform Downloads page, located at <ulink url="https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl..."/>.</para> <note> <para> For information on using the WOLF repository, see the <filename>readme</filename> file packaged with the quickstarts. @@ -17,35 +16,29 @@ </section> <section id="JBoss_Developer_Studio_or_Eclipse_with_JBoss_Tools"> <title>JBoss Developer Studio or Eclipse with JBoss Tools</title> - <remark>Aakanksha, this should be a <procedure>, not an itemized list.</remark> - <itemizedlist> - <listitem> +<procedure> + <title>Lauching JBoss Tools with Eclipse or JBoss Developer Studio</title> + <step> <para> - In your Workbench, go to - <code>File > New > Example... > JBoss Tools > Project Examples</code> + In your Workbench, go to<code>File > New > Example... > JBoss Tools > Project Examples</code> </para> - </listitem> - <listitem> + </step> + <step> <para> - In the New Project Example dialog, select the Site - <code>JBoss Community JBoss Portal Platform Examples</code> - from the drop down menu + In the New Project Example dialog, select the Site <code>JBoss Community JBoss Portal Platform Examples</code>from the drop down menu. </para> - </listitem> - <listitem> - <para> - Select one of the available Quickstarts, e.g. - <code>Simplest Hello World Portlet</code> + </step> + <step> + <para> + Select one of the available Quickstarts, e.g.<code>Simplest Hello World Portlet</code> </para> - </listitem> - <listitem> + </step> + <step> <para> - Click - <code>Finish</code> - and the example project will be imported into your workspace. + Click <code>Finish</code> and the example project will be imported into your workspace. </para> - </listitem> - </itemizedlist> + </step> +</procedure> <note> <para> For more information on how to use and deploy quickstarts, refer to the <filename>readme</filename> file <remark>packaged with</remark>of the quickstart.

11 years, 2 months

1
0
0 / 0

gatein SVN: r9193 - in epp/docs/branches/6.0/Reference_Guide/en-US: modules/AuthenticationAndIdentity and 1 other directory.

by do-not-reply＠jboss.org

Author: rdickens Date: 2013-03-03 22:54:54 -0500 (Sun, 03 Mar 2013) New Revision: 9193 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml Log: Incremented pubsnumber to get book re-Brew-ed Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-03-03 15:57:47 UTC (rev 9192) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-03-04 03:54:54 UTC (rev 9193) @@ -7,7 +7,21 @@ <title>Revision History</title> <simpara> <revhistory> - <revision> + <revision> + <revnumber>6.0.0-55</revnumber> + <date>Mon Mar 4 2013</date> + <author> + <firstname>Russell</firstname> + <surname>Dickenson</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>BZ#911516 - Incorporated new QE Review comments.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>6.0.0-54</revnumber> <date>Mon Mar 4 2013</date> <author> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-03-03 15:57:47 UTC (rev 9192) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-03-04 03:54:54 UTC (rev 9193) @@ -49,7 +49,7 @@ <para> Authentication workflow consists of HTTP requests and redirects which include handshakes. Currently only Servlet 3.0 containers are supported, so authentication is triggered programmatically from Servlet API. </para> - <para>In <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename>, authentication is triggered by accessing a secured URL <systemitem> /dologin</systemitem>: + <para>In <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename>, authentication is triggered by accessing a secured URL <systemitem>/dologin</systemitem>: </para> <programlisting language="XML"> <security-constraint> @@ -66,7 +66,8 @@ <transport-guarantee>NONE</transport-guarantee> </user-data-constraint> </web-resource-collection> -</security-constraint> </programlisting> +</security-constraint> +</programlisting> <para> This means that access to URLs (such as <ulink url="http://localhost:8080/portal/dologin" type="http">http://localhost:8080/portal/dologin</ulink>) will directly trigger J2EE authentication in the case that the user is not already logged in. </para> @@ -158,7 +159,7 @@ <term>JBossAS7LoginModule</term> <listitem> <para> - Most important login module, which is normally used to perform the whole authentication by itself. First it checks if Identity object has been already created and saved into sharedState map by previous login modules (like SSODelegateLoginModule, CustomMembershipLoginModule or SharedStateLoginModule). If not, it triggers real authentication of user with usage of Authenticator interface and it will use <filename>Authentication.validateUser(Credential[] credentials)</filename> which performs real authentication of username and password against OrganizationService and portal identity database. See <xref linkend="sect-Authentication_Authorization_Intro-authenticatorAndRolesExtractor"/> for details about Authenticator and about Identity objects. </para> + The most important login module, which is normally used to perform the whole authentication by itself. First it checks if an Identity object has been already created and saved into the sharedState map by previous login modules (like SSODelegateLoginModule, CustomMembershipLoginModule or SharedStateLoginModule). If not, it triggers real authentication of the user with usage of the Authenticator interface and it will use <filename>Authentication.validateUser(Credential[] credentials)</filename> which performs real authentication of username and password against OrganizationService and the portal identity database. See <xref linkend="sect-Authentication_Authorization_Intro-authenticatorAndRolesExtractor"/> for details about Authenticator and about Identity objects. </para> <para>In the <filename>JBossAS7LoginModule.commit</filename> method, the Identity object is registered to IdentityRegistry, which will be used later for authorization. Also some JAAS principals (UserPrincipal and RolesPrincipal) are assigned to our authenticated Subject. This is needed for JBoss Enterprise Application server, so that it can properly recognize the name of the logged user and its roles on an application server level. </para> </listitem> @@ -175,7 +176,7 @@ Special login module, which can be used to add a user to existing groups during a successful login of this user. The group name is configurable and by default is /platform/users group. This login module is not used because in normal environment, users are already in the /platform/users group. It is useful only for some special setups like read-only LDAP, where groups of an LDAP user are taken from the LDAP tree so that users may not be in the /platform/users group, which is needed for successful authorization. </para> <para> - Note that the CustomMembershipLoginModule can't be the first login module in the LoginModule chain because it assumes that the Identity object is already available in shared state. So there are two possible cases. For a non-SSO case, you may need to chain this login module with other login modules, which can be used to establish Identity and add it into shared state. Those login modules can be <filename>InitSharedStateLoginModule</filename> and <filename>SharedStateLoginModule</filename>. For an SSO case, you can add <filename>CustomMembershipLoginModule</filename> between <filename>SSODelegateLoginModule</filename> and JBossAS7LoginModule. + Note that the CustomMembershipLoginModule cannot be the first login module in the LoginModule chain because it assumes that the Identity object is already available in the shared state. So there are two possible cases. For a non-SSO case, you may need to chain this login module with other login modules, which can be used to establish Identity and add it into shared state. Those login modules can be <filename>InitSharedStateLoginModule</filename> and <filename>SharedStateLoginModule</filename>. For an SSO case, you can add <filename>CustomMembershipLoginModule</filename> between <filename>SSODelegateLoginModule</filename> and JBossAS7LoginModule. </para> </listitem> </varlistentry> @@ -191,7 +192,7 @@ <term>SharedStateLoginModule</term> <listitem> <para> - It reads username and password from sharedState map from attributes <literal>javax.security.auth.login.name</literal> and <literal>javax.security.auth.login.password</literal>. Then it calls Authenticator.validateUser(Credential[] credentials), to perform authentication of username and password against OrganizationService and portal identity database. Result of successful authentication is Identity object, which is saved to sharedState map. + It reads the username and password from sharedState map from attributes <literal>javax.security.auth.login.name</literal> and <literal>javax.security.auth.login.password</literal>. Then it calls Authenticator.validateUser(Credential[] credentials), to perform authentication of username and password against OrganizationService and portal identity database. The result of successful authentication is an Identity object, which is saved to the sharedState map. </para> </listitem> </varlistentry> @@ -265,11 +266,11 @@ <formalpara id="form-Authentication_Authorization_Intro-authenticationAppServerLevel"> <title>Authentication on Application Server Level</title> <para> - Application server needs to properly recognize that user is successfully logged and it has his JAAS roles assigned. Unfortunately this part is not standardized and is specific for each aaplication server. For example in JBoss Enterprise Application, you need to ensure that JAAS Subject has an assigned UserPrincipal with username and also a RolesPrincipal, which contains a list of JAAS roles. This part is actually done in <code>JbossAS7LoginModule.commit()</code>. In Tomcat, for example, this flow is little different, which means Tomcat has it is own <literal>TomcatLoginModule</literal>. + Application server needs to properly recognize that the user is successfully logged and it has their JAAS roles assigned. Unfortunately this part is not standardized and is specific for each aaplication server. For example in JBoss Enterprise Application Platform, you need to ensure that JAAS Subject has an assigned UserPrincipal with username and also a RolesPrincipal, which contains a list of JAAS roles. This part is actually done in <code>JBossAS7LoginModule.commit()</code>. In Tomcat, for example, this flow is little different, which means Tomcat has it is own <literal>TomcatLoginModule</literal>. </para> </formalpara> <para> - After successful authentication, user needs to be at least in JAAS role "users" because this role is declared in <filename>web.xml</filename> as you saw above. JAAS roles are extracted by special algorithm from JBoss Portal Platform memberships. See below in section with RolesExtractor. + After successful authentication, user needs to be at least in JAAS role <systemitem>users</systemitem> because this role is declared in <filename>web.xml</filename> as you saw above. JAAS roles are extracted by special algorithm from JBoss Portal Platform memberships. See below in section with RolesExtractor. </para> <formalpara id="form-Authentication_Authorization_Intro-authenticationGateInServerLevel"> <title>Authentication on JBoss Portal Platform Level</title> @@ -307,20 +308,20 @@ ]]> </programlisting> <para> - Method <emphasis>validateUser</emphasis> is used to check whether given credentials (username and password) are really valid. So it performs real authentication. It returns a username if the credentials are correct. Otherwise LoginException is thrown. + Method <emphasis>validateUser</emphasis> is used to authenticate the given credentials (username and password). It returns a username if the credentials are correct, otherwise a <computeroutput>LoginException</computeroutput> is thrown. </para> <para> - Method <emphasis>createIdentity</emphasis> is used to create instance of object <emphasis>org.exoplatform.services.security.Identity</emphasis>, which encapsulates all important information about a single user: + Method <emphasis>createIdentity</emphasis> is used to create an instance of object <emphasis>org.exoplatform.services.security.Identity</emphasis>, which encapsulates all important information about a single user: </para> <itemizedlist> <listitem> <para> - username + Username </para> </listitem> <listitem> <para> - set of Memberships (MembershipEntry objects) which user has. <emphasis>Membership</emphasis> is object, which contains information about <emphasis>membershipType</emphasis> (manager, member, validator, ... ) and about <emphasis>group</emphasis> (/platform/users, /platform/administrators, /partners, /organization/management/executiveBoard, ... ). + Set of Memberships (MembershipEntry objects) associated with the <systemitem>user</systemitem>. <emphasis>Membership</emphasis> is an object, which contains information about <emphasis>membershipType</emphasis> (manager, member, validator, ... ) and about <emphasis>group</emphasis> (/platform/users, /platform/administrators, /partners, /organization/management/executiveBoard, ... ). </para> </listitem> <listitem> @@ -386,24 +387,24 @@ <section id="sect-Authentication_Authorization_Intro-RememberMeAuthentication"> <title>RememberMe Authentication</title> <para> - In default login dialog, you can notice that there is "Remember my login" checkbox, which users can use to persist their login on his workstation. Default validity period of RememberMe cookie is one day (it is configurable), and so user can be logged for whole day before he need to re-authenticate. + In the default login dialog is the <screen>Remember my login</screen> checkbox, which persist a user's login on their workstation. The default validity period of the <systemitem>RememberMe</systemitem> cookie is one day, so a user can be logged for a whole day before needing to re-authenticate. The validity period is configurable. </para> <section id="sect-Authentication_Authorization_Intro-RememberMeAuthentication-howDoesItWork"> <title>How It Works</title> <itemizedlist> <listitem> <para> - User checks the checkbox "Remember my login" on login screen of JBoss Portal Platform . Then submits the form. + User checks the checkbox <systemitem>RememberMe</systemitem> on the login screen of JBoss Portal Platform, then submits the form. </para> </listitem> <listitem> <para> - HTTP request like <ulink url="http://localhost:8080/portal/login?initialURI=/portal/classic&amp;use..."/> is sent to server. This is not a HTTP GET request and the parameters are not encoded in URL. The login form is submitted in a HTTP POST request to the /portal/login URL. + A HTTP request such as <ulink url="http://localhost:8080/portal/login?initialURI=/portal/classic&amp;use..."/> is sent to the server. This is not a HTTP GET request and the parameters are not encoded in the URL. The login form is submitted in a HTTP POST request to the /portal/login URL. </para> </listitem> <listitem> <para> - Request is processed by PortalLoginController servlet. The servlet obtains instance of <emphasis>RemindPasswordTokenService</emphasis> and saves user credentials into JCR. It generates and returns special token (key) for later use. Then it creates cookie called <emphasis>RememberMe</emphasis> and use returned token as value of cookie. + Request is processed by PortalLoginController servlet. The servlet obtains an instance of <emphasis>RemindPasswordTokenService</emphasis> and saves user credentials into JCR. It generates and returns special token (key) for later use, then creates a cookie called <emphasis>RememberMe</emphasis> and uses the returned token as the cookie's value. </para> </listitem> </itemizedlist> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2013-03-03 15:57:47 UTC (rev 9192) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2013-03-04 03:54:54 UTC (rev 9193) @@ -393,7 +393,7 @@ <title>Configuration Files</title> <para> The main configuration file is - <code>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/idm-configuration.xml</code> + <filename><replaceable>JPP_HOME</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/idm-configuration.xml</filename> : </para> <informalexample> @@ -540,12 +540,12 @@ <listitem> <para> <code>defaultGroupType</code> - The name of the PicketLink IDM GroupType that will be used to store groups. The default is<code>'GTN_GROUP_TYPE'</code>. + The name of the PicketLink IDM GroupType that will be used to store groups. The default is <code>GTN_GROUP_TYPE</code>. </para> </listitem> <listitem> <para> - <code>rootGroupName</code> The name of the PicketLink IDM Group that will be used as a root parent. The default is <code>'GTN_ROOT_GROUP'</code>. + <code>rootGroupName</code> The name of the PicketLink IDM Group that will be used as a root parent. The default is <code>GTN_ROOT_GROUP</code>. </para> </listitem> <listitem> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml 2013-03-03 15:57:47 UTC (rev 9192) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml 2013-03-04 03:54:54 UTC (rev 9193) @@ -16,17 +16,17 @@ <para> Default implementation of <code>CredentialEncoder</code> - is using password hashing with MD5 algorithm and storing those MD5 hashes in database. It does not use any salting of passwords. This is not safest solution, but it's backward compatible with previous releases of JBoss Portal Platform before version 6, where MD5 password hashing was the only possible encoding form. So if you migrate from older release of JBoss Portal Platform, your users will still be able to authenticate. + is using password hashing with MD5 algorithm and storing those MD5 hashes in database. It does not use any salting of passwords. This is not safest solution, but it is backward compatible with previous releases of JBoss Portal Platform before version 6, where MD5 password hashing was the only possible encoding form. So if you migrate from older release of JBoss Portal Platform, your users will still be able to authenticate. </para> <para>However if you are starting from a fresh database (no migration from previous JBoss Portal Platform release), you may increase security by using better hashing algorithm and especially by enabling password salting. See below for details.</para> <section id="sid-54264610_PasswordEncryption-ChoosingCredentialEncoderimplementation"> <title>Choosing CredentialEncoder Implementation</title> <para> -The implementation of CredentialEncoder is configured in file <code>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml</code>. Usually the most important options are the options of the <code>idm_portal</code> realm starting with <code>credentialEncoder</code> prefix. Possible implementations are HashingEncoder, DatabaseReadingSaltEncoder, and FileReadingSaltEncoder. +The implementation of CredentialEncoder is configured in file <filename><replaceable>JPP_HOME</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml</filename>. Usually the most important options are the options of the <code>idm_portal</code> realm starting with <code>credentialEncoder</code> prefix. Possible implementations are HashingEncoder, DatabaseReadingSaltEncoder, and FileReadingSaltEncoder. </para> <section id="sid-54264610_PasswordEncryption-HashingEncoder"> <title>HashingEncoder</title> - <para>This is the default choice. It uses only hashing of passwords with MD5 algorithm without salting. As mentioned previously, it is not the safest solution but it's backward compatible with the previous JBoss Portal Platform releases, so there are no issues with database migration. Configuration looks like this:</para> + <para>This is the default choice. It uses only hashing of passwords with MD5 algorithm without salting. As mentioned previously, it is not the safest solution but it is backward compatible with the previous JBoss Portal Platform releases, so there are no issues with database migration. Configuration looks like this:</para> <informalexample> <programlisting> <option> @@ -42,7 +42,7 @@ </section> <section id="sid-54264610_PasswordEncryption-DatabaseReadingSaltEncoder"> <title>DatabaseReadingSaltEncoder</title> - <para>This implementation provides salting of password in addition to hashing. The salt is unique for each user, so it's much more complicated to decrypt password via brute force, if some attacker steals encoded passwords from your database. The salt is generated randomly for each user and stored in PicketLink IDM database as an attribute. Random generation of salt ensures that all users have different salts, so even if two users have the same password, the encoded password in database will be different for them. Here is configuration example, which is using SHA-256 algorithm for hashing (more secure than MD5) and algorithm SHA1PRNG for generation of random salts.</para> + <para>This implementation provides salting of password in addition to hashing. The salt is unique for each user, so it is much more complicated to decrypt password via brute force, if an attacker steals encoded passwords from your database. The salt is generated randomly for each user and stored in the PicketLink IDM database as an attribute. Random generation of salt ensures that all users have different salts, so even if two users have the same password, the encoded password in database will be different for them. Here is configuration example, which is using SHA-256 algorithm for hashing (more secure than MD5) and algorithm SHA1PRNG for generation of random salts.</para> <informalexample> <programlisting> <option> @@ -63,7 +63,7 @@ <section id="sid-54264610_PasswordEncryption-FileReadingSaltEncoder"> <title>FileReadingSaltEncoder</title> <para> - The FileReadingSaltEncoder also uses hashing and salting, so it's similar to the previous encoder. But it's theoretically even more secure, because salts are not stored in PicketLink IDM database together with passwords. Salt of each user is generated from <emphasis role="italics">saltPrefix</emphasis> and user's username. And <emphasis role="italics">saltPrefix</emphasis> is read from some file in your file system. Configuration can look like this: + The FileReadingSaltEncoder also uses hashing and salting, so it is similar to the previous encoder. But it is theoretically even more secure, because salts are not stored in the PicketLink IDM database together with passwords. Salt of each user is generated from <emphasis role="italics">saltPrefix</emphasis> and user's username. And <emphasis role="italics">saltPrefix</emphasis> is read from some file in your file system. Configuration can look like this: </para> <informalexample> <programlisting> @@ -82,15 +82,15 @@ </programlisting> </informalexample> <para> - Please note that specified file <code>/salt/mysalt.txt</code> must exist and must be readable by user, which executed JBoss Portal Platform. The file should be properly secured so that it is readable by every user of your OS. The content of the file can be a random phrase, such as <emphasis role="italics">a4564dac2aasddsklklkajdgnioiow</emphasis>. + Please note that specified file <code>/salt/mysalt.txt</code> must exist and must be readable by user, which executed JBoss Portal Platform. The file should be properly secured so that it is not readable by every user of your operating syste,. The content of the file can be a random phrase, such as: <emphasis role="italics">a4564dac2aasddsklklkajdgnioiow</emphasis>. </para> <para> -So the <code>FileReadingSaltEncoder</code>is probably the most secure of all options, but in addition to <code>DatabaseReadingSaltEncoder</code>, you need to set the file with salt. + The <code>FileReadingSaltEncoder</code>is probably the most secure of all options, but in addition to <code>DatabaseReadingSaltEncoder</code>, you need to set the file with salt. </para> <important> <title>Important</title> <para> - The <code>CredentialEncoder</code> from above is actually used only for encoding of passwords in PicketLink IDM database. It's not used for LDAP. PicketLink IDM LDAP implementation (<code>LDAPIdentityStore</code>) is sending passwords to LDAP server in plain form, because password encoding is usually provided by LDAP server itself. For example OpenDS 2 is using SHA1 based hashing of passwords with random generation of user salt (so actually something similar to our <code>DatabaseReadingSaltEncoder</code> implementation). + The <code>CredentialEncoder</code> from above is actually used only for encoding of passwords in PicketLink IDM database. It is not used for LDAP. PicketLink IDM LDAP implementation (<code>LDAPIdentityStore</code>) sends passwords to the LDAP server in plain form, because password encoding is usually provided by LDAP server itself. For example OpenDS 2 is using SHA1 based hashing of passwords with random generation of user salt (so actually something similar to our <code>DatabaseReadingSaltEncoder</code> implementation). </para> </important> </section>

11 years, 2 months

1
0
0 / 0

gatein SVN: r9192 - in epp/docs/branches/6.0/Reference_Guide/en-US: modules/AuthenticationAndIdentity and 1 other directory.

by do-not-reply＠jboss.org

Author: aakanksha_writer Date: 2013-03-03 10:57:47 -0500 (Sun, 03 Mar 2013) New Revision: 9192 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AccessingUserProfile.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SAML2.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SAML2_Salesforce_and_Google_Integration.xml Log: BZ#911516,856448,856430 updated Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-03-01 06:46:33 UTC (rev 9191) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-03-03 15:57:47 UTC (rev 9192) @@ -7,6 +7,20 @@ <title>Revision History</title> <simpara> <revhistory> + <revision> + <revnumber>6.0.0-54</revnumber> + <date>Mon Mar 4 2013</date> + <author> + <firstname>Aakanksha</firstname> + <surname>Singh</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>BZ#911516,856448,856430 - Incorporated new QE Review comments.</member> + </simplelist> + </revdescription> + </revision> <revision> <revnumber>6.0.0-53</revnumber> <date>Wed Feb 27 2013</date> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AccessingUserProfile.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AccessingUserProfile.xml 2013-03-01 06:46:33 UTC (rev 9191) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AccessingUserProfile.xml 2013-03-03 15:57:47 UTC (rev 9192) @@ -22,6 +22,6 @@ </listitem> </orderedlist> <para> - Both alternatives are probably better then {{OrganizationService orgService = getApplicationComponent(OrganizationService.class)}} because you can use them from your own portlets or servlet/portlet filters. The variant with {{getApplicationComponent}} works only from WebUI. + Both alternatives are probably better than <code>OrganizationService orgService = getApplicationComponent(OrganizationService.class)</code> because you can use them from your own portlets or servlet/portlet filters. The variant with <literal>getApplicationComponent</literal> works only from WebUI. </para> </chapter> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-03-01 06:46:33 UTC (rev 9191) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-03-03 15:57:47 UTC (rev 9192) @@ -49,9 +49,10 @@ <para> Authentication workflow consists of HTTP requests and redirects which include handshakes. Currently only Servlet 3.0 containers are supported, so authentication is triggered programmatically from Servlet API. </para> - <para>In <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename>, authentication is triggered by accessing a secured URL <systemitem>_/dologin_</systemitem>: + <para>In <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename>, authentication is triggered by accessing a secured URL <systemitem> /dologin</systemitem>: </para> - <programlisting language="XML"><security-constraint> + <programlisting language="XML"> +<security-constraint> <web-resource-collection> <web-resource-name>user authentication</web-resource-name> <url-pattern>/dologin</url-pattern> @@ -70,7 +71,7 @@ This means that access to URLs (such as <ulink url="http://localhost:8080/portal/dologin" type="http">http://localhost:8080/portal/dologin</ulink>) will directly trigger J2EE authentication in the case that the user is not already logged in. </para> <para> - Access to this URL also means that the user needs to be in the JAAS group <emphasis>users</emphasis>, otherwise they can authenticate but will receive an HTTP error: <emphasis>403 Forbidden</emphasis>, for example. + Access to this URL means that the user needs to be in the JAAS group <emphasis>users</emphasis>, otherwise they can authenticate but will receive an HTTP error: <emphasis>403 Forbidden</emphasis>. </para> <para> In the next part of the file we can see that authentication is FORM based and it starts by redirection to <emphasis>/login</emphasis> URL, which is mapped to <literal>LoginServlet</literal>. @@ -101,7 +102,7 @@ Changes to the appearance of this login page can be made in this JSP file. Alternatively you can create an extension and override this page via extension if you don't want to edit it directly. You can also change images or CSS placed in <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/login/skin</filename>. </para> <para> - After a user submits the login form, they are redirected to the login URL: <ulink url="http://localhost:8080/portal/login?username=root&password=gtn&ini..." type="http">http://localhost:8080/portal/login?username=root&password=gtn&ini...</ulink>. + After a user submits the login form, the LoginServlet will store credentials and trigger WCI login, which delegates to Servlet API (method HttpServletRequest.login(String username, String password) available in Servlet 3.0) and additionally triggers WCI Authentication listeners. Login through Servlet API delegates to JAAS. </para> <para> This URL is mapped to <literal>LoginServlet</literal> servlet, which stores credentials and redirects again to <literal>LoginServlet</literal>. LoginServlet triggers WCI login, which delegates to Servlet API (method HttpServletRequest.login(String username, String password) available in Servlet 3.0) and additionally triggers WCI Authentication listeners. Login through Servlet API delegates to JAAS. @@ -125,7 +126,7 @@ <module-option name="realmName" value="gatein-domain" /> <module-option name="password-stacking" value="useFirstPass" /> </login-module> - <login-module code="org.exoplatform.services.security.j2ee.JBossEAP6LoginModule" flag="required"> + <login-module code="org.exoplatform.services.security.j2ee.JBossAS7LoginModule" flag="required"> <module-option name="portalContainerName" value="portal"/> <module-option name="realmName" value="gatein-domain"/> </login-module> @@ -149,22 +150,22 @@ <term>SSODelegateLoginModule</term> <listitem> <para> - It is useful only if SSO authentication is enabled (disabled by default. It can be enabled through properties in configuration.properties file and in this case it delegates the work to another real login module for SSO integration. If SSO is disabled, SSODelegateLoginModule is simply ignored. See <xref linkend="sect-SSO_Single_Sign_On_-Central_Authentication_Service"/> properties details for more details. If SSO is used and SSO authentication succeed, the special Identity object will be created and saved into shared state map (Map, which is shared between all login modules), so that this Identity object can be used by JBoss Enterprise Application Platform 6 LoginModule or other login modules in the JAAS chain. + It is useful only if SSO authentication is enabled (disabled by default). SSO authentication can be enabled through properties in <filename>configuration.properties</filename> file and it delegates the work to another real login module for SSO integration. If SSO is disabled, <filename>SSODelegateLoginModule</filename> is simply ignored. See <xref linkend="sect-SSO_Single_Sign_On_-Central_Authentication_Service"/> properties for more details. If SSO is used and SSO authentication succeeds, the special Identity object is created and saved into shared state map (Map, which is shared between all login modules), so that this Identity object can be used by JBossAS7LoginModule or other login modules in the JAAS chain. </para> </listitem> </varlistentry> <varlistentry> - <term>JBoss Enterprise Application Platform 6 LoginModule</term> + <term>JBossAS7LoginModule</term> <listitem> <para> - Most important login module, which is normally used to perform whole authentication by itself. First it checks if Identity object has been already created and saved into sharedState map by previous login modules (like SSODelegateLoginModule, CustomMembershipLoginModule or SharedStateLoginModule). If not, it triggers real authentication of user with usage of Authenticator interface and it will use Authentication.validateUser(Credential[] credentials) which performs real authentication of username and password against OrganizationService and portal identity database. See <xref linkend="sect-Authentication_Authorization_Intro-authenticatorAndRolesExtractor"/> for details about Authenticator and about Identity objects. </para> - <para>In the JBoss Enterprise Application Platform 6 LoginModule.commit method, the Identity object is registered to IdentityRegistry, which will be used later for authorization. Also some JAAS principals (UserPrincipal and RolesPrincipal) and assigned to our authenticated Subject. This is needed for JBoss Enterprise Application server, so that it can properly recognize the name of the logged user and its roles on an JBoss Enterprise Application level. + Most important login module, which is normally used to perform the whole authentication by itself. First it checks if Identity object has been already created and saved into sharedState map by previous login modules (like SSODelegateLoginModule, CustomMembershipLoginModule or SharedStateLoginModule). If not, it triggers real authentication of user with usage of Authenticator interface and it will use <filename>Authentication.validateUser(Credential[] credentials)</filename> which performs real authentication of username and password against OrganizationService and portal identity database. See <xref linkend="sect-Authentication_Authorization_Intro-authenticatorAndRolesExtractor"/> for details about Authenticator and about Identity objects. </para> + <para>In the <filename>JBossAS7LoginModule.commit</filename> method, the Identity object is registered to IdentityRegistry, which will be used later for authorization. Also some JAAS principals (UserPrincipal and RolesPrincipal) are assigned to our authenticated Subject. This is needed for JBoss Enterprise Application server, so that it can properly recognize the name of the logged user and its roles on an application server level. </para> </listitem> </varlistentry> </variablelist> <para> - Some other login modules are not active by default, but can be added them if you find them useful. + Some other login modules are not active by default, but can be added if needed. </para> <variablelist> <varlistentry> @@ -174,7 +175,7 @@ Special login module, which can be used to add a user to existing groups during a successful login of this user. The group name is configurable and by default is /platform/users group. This login module is not used because in normal environment, users are already in the /platform/users group. It is useful only for some special setups like read-only LDAP, where groups of an LDAP user are taken from the LDAP tree so that users may not be in the /platform/users group, which is needed for successful authorization. </para> <para> - Note that the CustomMembershipLoginModule can't be the first login module in the LoginModule chain because it assumes that the Identity object is already available in shared state. So there are two possible cases. For an non-SSO case, you may need to chain this LM with other login modules, which can be used to establish Identity and add it into shared state. Those LM can be InitSharedStateLoginModule and SharedStateLoginModule. For an SSO case, you can add CustomMembershipLoginModule between SSODelegateLoginModule and JBoss Enterprise Application Platform 6 LoginModule. + Note that the CustomMembershipLoginModule can't be the first login module in the LoginModule chain because it assumes that the Identity object is already available in shared state. So there are two possible cases. For a non-SSO case, you may need to chain this login module with other login modules, which can be used to establish Identity and add it into shared state. Those login modules can be <filename>InitSharedStateLoginModule</filename> and <filename>SharedStateLoginModule</filename>. For an SSO case, you can add <filename>CustomMembershipLoginModule</filename> between <filename>SSODelegateLoginModule</filename> and JBossAS7LoginModule. </para> </listitem> </varlistentry> @@ -190,7 +191,7 @@ <term>SharedStateLoginModule</term> <listitem> <para> - It reads username and password from sharedState map from attributes javax.security.auth.login.name and javax.security.auth.login.password. Then it calls Authenticator.validateUser(Credential[] credentials), to perform authentication of username and password against OrganizationService and portal identity database. Result of successful authentication is object Identity, which is saved to sharedState map. + It reads username and password from sharedState map from attributes <literal>javax.security.auth.login.name</literal> and <literal>javax.security.auth.login.password</literal>. Then it calls Authenticator.validateUser(Credential[] credentials), to perform authentication of username and password against OrganizationService and portal identity database. Result of successful authentication is Identity object, which is saved to sharedState map. </para> </listitem> </varlistentry> @@ -213,13 +214,13 @@ <module-option name="membershipType" value="member" /> <module-option name="groupId" value="/platform/users" /> </login-module> - <login-module code="org.exoplatform.services.security.j2ee.JBossEAP6LoginModule" flag="required"> + <login-module code="org.exoplatform.services.security.j2ee.JBossAS7LoginModule" flag="required"> <module-option name="portalContainerName" value="portal"/> <module-option name="realmName" value="gatein-domain"/> </login-module>]]> </programlisting> <para> - And a configuration example with enabled SSO: + Configuration example with enabled SSO: </para> <programlisting language="XML" role="XML"><![CDATA[ <login-module code="org.gatein.sso.integration.SSODelegateLoginModule" flag="required"> @@ -235,7 +236,7 @@ <module-option name="membershipType" value="member" /> <module-option name="groupId" value="/platform/users" /> </login-module> - <login-module code="org.exoplatform.services.security.j2ee.JBossEAP6LoginModule" flag="required"> + <login-module code="org.exoplatform.services.security.j2ee.JBossAS7LoginModule" flag="required"> <module-option name="portalContainerName" value="portal"/> <module-option name="realmName" value="gatein-domain"/> </login-module>]]> @@ -264,8 +265,7 @@ <formalpara id="form-Authentication_Authorization_Intro-authenticationAppServerLevel"> <title>Authentication on Application Server Level</title> <para> - <remark>QUESTION: Should the following reference to Tomcat be removed?</remark> - Application server needs to properly recognize that user is successfully logged and it has assigned his JAAS roles. Unfortunately this part is not standardized and is specific for each AS. For example in JBoss Enterprise Application, you need to ensure that JAAS Subject has assigned principal with username (UserPrincipal) and also RolesPrincipal, which has name "Roles" and it contains list of JAAS roles. This part is actually done in <code>JbossLoginModule.commit()</code>. In Tomcat, this flow is little different, which means Tomcat has it is own <literal>TomcatLoginModule</literal>. + Application server needs to properly recognize that user is successfully logged and it has his JAAS roles assigned. Unfortunately this part is not standardized and is specific for each aaplication server. For example in JBoss Enterprise Application, you need to ensure that JAAS Subject has an assigned UserPrincipal with username and also a RolesPrincipal, which contains a list of JAAS roles. This part is actually done in <code>JbossAS7LoginModule.commit()</code>. In Tomcat, for example, this flow is little different, which means Tomcat has it is own <literal>TomcatLoginModule</literal>. </para> </formalpara> <para> @@ -307,7 +307,7 @@ ]]> </programlisting> <para> - Method <emphasis>validateUser</emphasis> is used to check whether given credentials (username and password) are really valid. So it performs real authentication. It returns back username if credentials are correct. Otherwise LoginException is thrown. + Method <emphasis>validateUser</emphasis> is used to check whether given credentials (username and password) are really valid. So it performs real authentication. It returns a username if the credentials are correct. Otherwise LoginException is thrown. </para> <para> Method <emphasis>createIdentity</emphasis> is used to create instance of object <emphasis>org.exoplatform.services.security.Identity</emphasis>, which encapsulates all important information about a single user: @@ -320,7 +320,7 @@ </listitem> <listitem> <para> - set of Memberships (MembershipEntry objects) which user belongs to. <emphasis>Membership</emphasis> is object, which contains information about <emphasis>membershipType</emphasis> (manager, member, validator, ... ) and about <emphasis>group</emphasis> (/platform/users, /platform/administrators, /partners, /organization/management/executiveBoard, ... ). + set of Memberships (MembershipEntry objects) which user has. <emphasis>Membership</emphasis> is object, which contains information about <emphasis>membershipType</emphasis> (manager, member, validator, ... ) and about <emphasis>group</emphasis> (/platform/users, /platform/administrators, /partners, /organization/management/executiveBoard, ... ). </para> </listitem> <listitem> @@ -386,10 +386,10 @@ <section id="sect-Authentication_Authorization_Intro-RememberMeAuthentication"> <title>RememberMe Authentication</title> <para> - In default login dialog, you can notice that there is "Remember my login" checkbox, which users can use to persist their login on his workstation. Default validity period of RememberMe cookie is one day (it is configurable), and so user can be logged for whole day before he need to re-authenticate again with his credentials. + In default login dialog, you can notice that there is "Remember my login" checkbox, which users can use to persist their login on his workstation. Default validity period of RememberMe cookie is one day (it is configurable), and so user can be logged for whole day before he need to re-authenticate. </para> <section id="sect-Authentication_Authorization_Intro-RememberMeAuthentication-howDoesItWork"> - <title>How Does It Work</title> + <title>How It Works</title> <itemizedlist> <listitem> <para> @@ -398,12 +398,12 @@ </listitem> <listitem> <para> - HTTP request like <ulink url="http://localhost:8080/portal/login?initialURI=/portal/classic&amp;use..."/> is sent to server. + HTTP request like <ulink url="http://localhost:8080/portal/login?initialURI=/portal/classic&amp;use..."/> is sent to server. This is not a HTTP GET request and the parameters are not encoded in URL. The login form is submitted in a HTTP POST request to the /portal/login URL. </para> </listitem> <listitem> <para> - Request is processed by PortalLoginController servlet. Servlet obtains instance of <emphasis>RemindPasswordTokenService</emphasis> and save user credentials into JCR. It generates and returns special token (key) for later use. Then it creates cookie called <emphasis>RememberMe</emphasis> and use returned token as value of cookie. + Request is processed by PortalLoginController servlet. The servlet obtains instance of <emphasis>RemindPasswordTokenService</emphasis> and saves user credentials into JCR. It generates and returns special token (key) for later use. Then it creates cookie called <emphasis>RememberMe</emphasis> and use returned token as value of cookie. </para> </listitem> </itemizedlist> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2013-03-01 06:46:33 UTC (rev 9191) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2013-03-03 15:57:47 UTC (rev 9192) @@ -110,8 +110,7 @@ <parameter>(value-param)</parameter> </para> <para> - If the <literal>config</literal> parameter is not provided, this parameter will be used to perform JNDI lookup for IdentitySessionFactory. - </para> + If the <literal>config</literal> parameter is not provided, this parameter will be used to perform JNDI lookup for IdentitySessionFactory.</para> </listitem> @@ -483,9 +482,7 @@ <section id="sid-54264613_PicketLinkIDMintegration-PicketlinkIDMServiceImpl"> <title>PicketlinkIDMServiceImpl</title> <para> - The - <code>org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl</code> - service has the following options: + The<code>org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl</code> service has the following options: </para> <itemizedlist> <listitem> @@ -496,54 +493,37 @@ </listitem> <listitem> <para> - <code>hibernate.properties</code> - (properties-param) A list of hibernate properties used to create SessionFactory that will be injected to JBoss Identity IDM configuration registry. + <code>hibernate.properties</code> (properties-param) A list of hibernate properties used to create SessionFactory that will be injected to JBoss Identity IDM configuration registry. </para> </listitem> <listitem> <para> - <code>hibernate.annotations</code> - A list of annotated classes that will be added to Hibernate configuration. + <code>hibernate.annotations</code> A list of annotated classes that will be added to Hibernate configuration. </para> </listitem> <listitem> <para> - <code>hibernate.mappings</code> - A list of - <code>.xml</code> - files that will be added to hibernate configuration as mapping files. + <code>hibernate.mappings</code> A list of <code>.xml</code> files that will be added to hibernate configuration as mapping files. </para> </listitem> <listitem> <para> - <code>jndiName</code> - (value-param) If the 'config' parameter is not provided, this parameter will be used to perform JNDI lookup for - <code>IdentitySessionFactory</code> - . + <code>jndiName</code> (value-param) If the 'config' parameter is not provided, this parameter will be used to perform JNDI lookup for <code>IdentitySessionFactory</code>. </para> </listitem> <listitem> <para> - <code>portalRealm</code> - (value-param) The realm name that should be used to obtain proper - <code>IdentitySession</code> - . The default is - <code>'PortalRealm'</code> - . + <code>portalRealm</code> (value-param) The realm name that should be used to obtain proper <code>IdentitySession</code>. The default is <code>'PortalRealm'</code>. </para> </listitem> <listitem> <para> - <code>apiCacheConfig</code> - (value-param) The Infinispan configuration file with cache configuration for PicketLink IDM API. It's different for cluster and non-cluster because Infinispan needs to be replicated in cluster environment. + <code>apiCacheConfig</code> (value-param) The Infinispan configuration file with cache configuration for PicketLink IDM API. It's different for cluster and non-cluster because Infinispan needs to be replicated in cluster environment. </para> </listitem> <listitem> <para> - <code>storeCacheConfig</code> - (value-param) - - The Infinispan configuration file with cache configuration for PicketLink IDM IdentityStore. Actually it's used only for LDAP store (not used with default DB configuration). It's different for cluster and non-cluster because Infinispan needs to be replicated in cluster environment. + <code>storeCacheConfig</code> (value-param). The Infinispan configuration file with cache configuration for PicketLink IDM IdentityStore. Actually it's used only for LDAP store (not used with default DB configuration). It's different for cluster and non-cluster because Infinispan needs to be replicated in cluster environment. </para> </listitem> </itemizedlist> @@ -551,90 +531,57 @@ <section id="sid-54264613_PicketLinkIDMintegration-PicketlinkIDMOrganizationServiceImpl"> <title>PicketlinkIDMOrganizationServiceImpl</title> <para> - The - <code>org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl</code> - key is a main entry point implementing - <code>org.exoplatform.services.organization.OrganizationService</code> - and is dependent on - <code>org.exoplatform.services.organization.idm.PicketLinkIDMService</code> - . + The <code>org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl</code> key is a main entry point implementing <code>org.exoplatform.services.organization.OrganizationService</code> and is dependent on <code>org.exoplatform.services.organization.idm.PicketLinkIDMService</code>. </para> <para> - The - <code>org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl</code> - service has the following options defined as fields of object-param of the - <code>org.exoplatform.services.organization.idm.Config</code> - type: + The<code>org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl</code> service has the following options defined as fields of object-param of the <code>org.exoplatform.services.organization.idm.Config</code> type: </para> <itemizedlist> <listitem> <para> <code>defaultGroupType</code> - The name of the PicketLink IDM GroupType that will be used to store groups. The default is - <code>'GTN_GROUP_TYPE'</code> - . + The name of the PicketLink IDM GroupType that will be used to store groups. The default is<code>'GTN_GROUP_TYPE'</code>. </para> </listitem> <listitem> <para> - <code>rootGroupName</code> - The name of the PicketLink IDM Group that will be used as a root parent. The default is - <code>'GTN_ROOT_GROUP'</code> - . + <code>rootGroupName</code> The name of the PicketLink IDM Group that will be used as a root parent. The default is <code>'GTN_ROOT_GROUP'</code>. </para> </listitem> <listitem> <para> - <code>passwordAsAttribute</code> - This parameter specifies if a password should be stored using PicketLink IDM Credential object or as a plain attribute. The default is - <code>false</code> - . + <code>passwordAsAttribute</code> This parameter specifies if a password should be stored using PicketLink IDM Credential object or as a plain attribute. The default is <code>false</code>. </para> </listitem> <listitem> <para> - <code>useParentIdAsGroupType</code> - This parameter stores the parent ID path as a group type in PicketLink IDM for any IDs not mapped with a specific type in 'groupTypeMappings'. If this option is set to - <code>false</code> - , and no mappings are provided under 'groupTypeMappings', then only one group with the given name can exist in the portal group tree. + <code>useParentIdAsGroupType</code> This parameter stores the parent ID path as a group type in PicketLink IDM for any IDs not mapped with a specific type in 'groupTypeMappings'. If this option is set to <code>false</code>, and no mappings are provided under 'groupTypeMappings', then only one group with the given name can exist in the portal group tree. </para> </listitem> <listitem> <para> <code>pathSeparator</code> - When 'userParentIdAsGroupType is set to - <code>true</code> - , this value will be used to replace all "/" characters in IDs. The "/" character is not allowed to be used in group type name in PicketLink IDM. + When 'userParentIdAsGroupType is set to <code>true</code>, this value will be used to replace all "/" characters in IDs. The "/" character is not allowed to be used in group type name in PicketLink IDM. </para> </listitem> <listitem> <para> - <code>associationMembershipType</code> - If this option is used, then each Membership, created with MembrshipType that is equal to the value specified here, will be stored in PicketLink IDM as simple Group-User association. + <code>associationMembershipType</code> If this option is used, then each Membership, created with MembrshipType that is equal to the value specified here, will be stored in PicketLink IDM as simple Group-User association. </para> </listitem> <listitem> <para> - <code>groupTypeMappings</code> - This parameter maps groups added with portal API as children of a given group ID, and stores them with a given group type name in PicketLink IDM. - - If the parent ID ends with "/*", then all child groups will have the mapped group type. Otherwise, only direct (first level) children will use this type. - - This can be leveraged by LDAP if LDAP DN is configured in PicketLink IDM to only store a specific group type. This will then store the given branch in portal group tree, while all other groups will remain in the database. + <code>groupTypeMappings</code> This parameter maps groups added with portal API as children of a given group ID, and stores them with a given group type name in PicketLink IDM. If the parent ID ends with "/*", then all child groups will have the mapped group type. Otherwise, only direct (first level) children will use this type. This can be leveraged by LDAP if LDAP DN is configured in PicketLink IDM to only store a specific group type. This will then store the given branch in portal group tree, while all other groups will remain in the database. </para> </listitem> <listitem> <para> - <code>forceMembershipOfMappedTypes</code> - Groups stored in PicketLink IDM with a type mapped in 'groupTypeMappings' will automatically be members under the mapped parent. Group relationships linked by PicketLink IDM group association will not be necessary. - - This parameter can be set to false if all groups are added via portal APIs. This may be useful with LDAP configuration as, when set to true, it will make every entry added to LDAP appear in portal. This, however, is not true for entries added via JBoss Portal Platform management user interface. + <code>forceMembershipOfMappedTypes</code> Groups stored in PicketLink IDM with a type mapped in 'groupTypeMappings' will automatically be members under the mapped parent. Group relationships linked by PicketLink IDM group association will not be necessary. This parameter can be set to false if all groups are added via portal APIs. This may be useful with LDAP configuration as, when set to true, it will make every entry added to LDAP appear in portal. This, however, is not true for entries added via JBoss Portal Platform management user interface. </para> </listitem> <listitem> <para> - <code>ignoreMappedMembershipType</code> - If "associationMembershipType" option is used, and this option is set to true, then Membership with MembershipType configured to be stored as PicketLink IDM association will not be stored as PicketLink IDM Role. + <code>ignoreMappedMembershipType</code> If "associationMembershipType" option is used, and this option is set to true, then Membership with MembershipType configured to be stored as PicketLink IDM association will not be stored as PicketLink IDM Role. </para> </listitem> </itemizedlist> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml 2013-03-01 06:46:33 UTC (rev 9191) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml 2013-03-03 15:57:47 UTC (rev 9192) @@ -16,23 +16,17 @@ <para> Default implementation of <code>CredentialEncoder</code> - is using password hashing with MD5 algorithm and storing those MD5 hashes in database. It does not use any salting of passwords. This is not safest solution, but it's backward compatible with previous releases of JBoss Portal Platform before version 3.5, where MD5 password hashing was only possible encoding form. So if you migrate from older release of JBoss Portal Platform, your users will be still able to authenticate. + is using password hashing with MD5 algorithm and storing those MD5 hashes in database. It does not use any salting of passwords. This is not safest solution, but it's backward compatible with previous releases of JBoss Portal Platform before version 6, where MD5 password hashing was the only possible encoding form. So if you migrate from older release of JBoss Portal Platform, your users will still be able to authenticate. </para> - <para>However if you are starting from fresh database (no migration from previous JBoss Portal Platform release), you may increase security by using better hashing algorithm and especially by enable password salting. See below for details.</para> + <para>However if you are starting from a fresh database (no migration from previous JBoss Portal Platform release), you may increase security by using better hashing algorithm and especially by enabling password salting. See below for details.</para> <section id="sid-54264610_PasswordEncryption-ChoosingCredentialEncoderimplementation"> <title>Choosing CredentialEncoder Implementation</title> <para> - The implementation of CredentialEncoder is configured in file - <code>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml</code> - . Usually the most important are options of realm - <code>idm_portal</code> - starting with prefix - <code>credentialEncoder.</code> - . Possible implementations are: +The implementation of CredentialEncoder is configured in file <code>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml</code>. Usually the most important options are the options of the <code>idm_portal</code> realm starting with <code>credentialEncoder</code> prefix. Possible implementations are HashingEncoder, DatabaseReadingSaltEncoder, and FileReadingSaltEncoder. </para> <section id="sid-54264610_PasswordEncryption-HashingEncoder"> <title>HashingEncoder</title> - <para>This is the default choice. It uses only hashing of passwords with MD5 algorithm without salting. As mentioned previously, it's not safest solution but it's backward compatible with previous JBoss Portal Platform releases, so there are no issues with database migration from previous release. Configuration looks like this:</para> + <para>This is the default choice. It uses only hashing of passwords with MD5 algorithm without salting. As mentioned previously, it is not the safest solution but it's backward compatible with the previous JBoss Portal Platform releases, so there are no issues with database migration. Configuration looks like this:</para> <informalexample> <programlisting> <option> @@ -48,7 +42,7 @@ </section> <section id="sid-54264610_PasswordEncryption-DatabaseReadingSaltEncoder"> <title>DatabaseReadingSaltEncoder</title> - <para>This implementation provides salting of password in addition to hashing. The salt is unique for each user, so it's much more complicated to decrypt password via brute force, if some attacker steal encoded passwords from your database. The salt is generated randomly for each user and stored in PicketLink IDM database as attribute. Random generation of salt ensure that all users have different salts, so even if two users have same password, the encoded password in database will be different for them. Here is configuration example, which is using SHA-256 algorithm for hashing (more secure than MD5) and algorithm SHA1PRNG for generation of random salts.</para> + <para>This implementation provides salting of password in addition to hashing. The salt is unique for each user, so it's much more complicated to decrypt password via brute force, if some attacker steals encoded passwords from your database. The salt is generated randomly for each user and stored in PicketLink IDM database as an attribute. Random generation of salt ensures that all users have different salts, so even if two users have the same password, the encoded password in database will be different for them. Here is configuration example, which is using SHA-256 algorithm for hashing (more secure than MD5) and algorithm SHA1PRNG for generation of random salts.</para> <informalexample> <programlisting> <option> @@ -69,11 +63,7 @@ <section id="sid-54264610_PasswordEncryption-FileReadingSaltEncoder"> <title>FileReadingSaltEncoder</title> <para> - It also uses hashing and salting, so it's similar like previous encoder. But it's theoretically even more secure, because salts are not stored in PicketLink IDM database together with passwords. Salt of each user is generated from - <emphasis role="italics">saltPrefix</emphasis> - and user's username. And - <emphasis role="italics">saltPrefix</emphasis> - is read from some file in your file system. Configuration can look like this: + The FileReadingSaltEncoder also uses hashing and salting, so it's similar to the previous encoder. But it's theoretically even more secure, because salts are not stored in PicketLink IDM database together with passwords. Salt of each user is generated from <emphasis role="italics">saltPrefix</emphasis> and user's username. And <emphasis role="italics">saltPrefix</emphasis> is read from some file in your file system. Configuration can look like this: </para> <informalexample> <programlisting> @@ -92,29 +82,15 @@ </programlisting> </informalexample> <para> - Please note that specified file - <code>/salt/mysalt.txt</code> - must exist and must be readable by user, which executed JBoss Portal Platform. But file should be properly secured to not be readable by every user of your OS. The file can have some random content phrase, for example - <emphasis role="italics">a4564dac2aasddsklklkajdgnioiow</emphasis> - . - </para> + Please note that specified file <code>/salt/mysalt.txt</code> must exist and must be readable by user, which executed JBoss Portal Platform. The file should be properly secured so that it is readable by every user of your OS. The content of the file can be a random phrase, such as <emphasis role="italics">a4564dac2aasddsklklkajdgnioiow</emphasis>. + </para> <para> - So the - <code>FileReadingSaltEncoder</code> - is probably most secure of all options, but in addition to - <code>DatabaseReadingSaltEncoder</code> - you need to set the file with salt. +So the <code>FileReadingSaltEncoder</code>is probably the most secure of all options, but in addition to <code>DatabaseReadingSaltEncoder</code>, you need to set the file with salt. </para> <important> <title>Important</title> <para> - The - <code>CredentialEncoder</code> - from above is actually used only for encoding of passwords in PicketLink IDM database. It's not used for LDAP. PicketLink IDM LDAP implementation ( - <code>LDAPIdentityStore</code> - ) is sending passwords to LDAP server in plain form, because password encoding is usually provided by LDAP server itself. For example OpenDS 2 is using SHA1 based hashing of passwords with random generation of user salt (so actually something similar to our - <code>DatabaseReadingSaltEncoder</code> - implementation). + The <code>CredentialEncoder</code> from above is actually used only for encoding of passwords in PicketLink IDM database. It's not used for LDAP. PicketLink IDM LDAP implementation (<code>LDAPIdentityStore</code>) is sending passwords to LDAP server in plain form, because password encoding is usually provided by LDAP server itself. For example OpenDS 2 is using SHA1 based hashing of passwords with random generation of user salt (so actually something similar to our <code>DatabaseReadingSaltEncoder</code> implementation). </para> </important> </section> @@ -139,38 +115,38 @@ </listitem> <listitem> <para> - Passwords can be encoded prior to being saved to the JCR. This option requires administrators to provide a custom subclass of <parameter>org.exoplatform.web.security.security.AbstractCodec</parameter> and set up a codec implementation with <parameter>CookieTokenService</parameter>: + Passwords can be encoded prior to being saved to the JCR. This option requires administrators to provide a custom subclass of <parameter>org.exoplatform.web.security.security.AbstractCodec</parameter> and set up a codec implementation with <parameter>CookieTokenService</parameter>: </para> <procedure id="proc-Reference_Guide-Password_Encryption-Encrypt_Password_in_JCR"> <title>Encrypt Password in JCR</title> <step> <para> - Create a Java class similar to: + Create a Java class similar to: </para> <programlisting language="Java" role="Java"><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../extras/Authentication_Identity/ExampleCodec.java" parse="text"/></programlisting> </step> <step> <para> - Compile the class and package it into a jar file. For this example we will call the jar file <filename>codec-example.jar</filename>. + Compile the class and package it into a jar file. For this example we will call the jar file <filename>codec-example.jar</filename>. </para> </step> <step> <para> - Create a <filename>conf/portal/configuration.xml</filename> file within the <filename>codec-example.jar</filename> similar to the example below. This allows the portal kernel to find and use the new codec implementation. + Create a <filename>conf/portal/configuration.xml</filename> file within the <filename>codec-example.jar</filename> similar to the example below. This allows the portal kernel to find and use the new codec implementation. </para> <programlisting language="XML" role="XML"><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../extras/Authentication_Identity/configuration.xml" parse="text"/></programlisting> </step> <step> <para> - Deploy the <filename>codec-example.jar</filename> into the <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/lib/</filename> directory. + Deploy the <filename>codec-example.jar</filename> into the <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/lib/</filename> directory. </para> </step> <step> <para> - Start (or restart) JBoss Portal Platform. + Start (or restart) JBoss Portal Platform. </para> <para> - Any passwords written to the JCR will now be encoded and not plain text. + Any passwords written to the JCR will now be encoded and not plain text. </para> </step> </procedure> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SAML2.xml =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SAML2_Salesforce_and_Google_Integration.xml =================================================================== (Binary files differ)

11 years, 2 months

1
0
0 / 0

gatein SVN: r9191 - epp/docs/branches/6.0/Release_Notes/en-US.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2013-03-01 01:46:33 -0500 (Fri, 01 Mar 2013) New Revision: 9191 Modified: epp/docs/branches/6.0/Release_Notes/en-US/6.0.0_Release_Notes.ent epp/docs/branches/6.0/Release_Notes/en-US/New_Features.xml epp/docs/branches/6.0/Release_Notes/en-US/Revision_History.xml Log: Release Note draft content as extracted from DocDash Modified: epp/docs/branches/6.0/Release_Notes/en-US/6.0.0_Release_Notes.ent =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/6.0.0_Release_Notes.ent 2013-03-01 05:49:11 UTC (rev 9190) +++ epp/docs/branches/6.0/Release_Notes/en-US/6.0.0_Release_Notes.ent 2013-03-01 06:46:33 UTC (rev 9191) @@ -9,6 +9,6 @@ <!ENTITY HOLDER "Red Hat, Inc">  -<!ENTITY VX "6 Beta"> -<!ENTITY VY "6.0 Beta"> -<!ENTITY VZ "6.0.0 Beta"> +<!ENTITY VX "6"> +<!ENTITY VY "6.0"> +<!ENTITY VZ "6.0.0"> Modified: epp/docs/branches/6.0/Release_Notes/en-US/New_Features.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/New_Features.xml 2013-03-01 05:49:11 UTC (rev 9190) +++ epp/docs/branches/6.0/Release_Notes/en-US/New_Features.xml 2013-03-01 06:46:33 UTC (rev 9191) @@ -1,7 +1,6 @@ -<?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="new_features"> <title>New Features</title> <section> @@ -11,24 +10,32 @@ <section> <title>JSF 2.1 and RichFaces 4.2</title> <para> - The Portlet Bridge technology for JBoss Portal Platform 6 Beta has been updated to use JavaServer Faces 2.1 and RichFaces 4.2. + The Portlet Bridge technology for JBoss Portal Platform 6 has been updated to use JavaServer Faces 2.1 and RichFaces 4.2. </para> </section> <section> <title>SAML 2.0 for SSO</title> - <para>Authentication via SAML 2.0 is available in JBoss Portal Platform 6 Beta. The following SAML 2.0 profiles and bindings are available.</para> + <para>Authentication through SAML 2.0 is available in JBoss Portal Platform 6 . The following SAML 2.0 profiles and bindings are available.</para> <itemizedlist> <title>Available SAML 2.0 Profiles</title> - <listitem><para>Web Browser SSO</para></listitem> - <listitem><para>Single Logout</para></listitem> + <listitem> + <para>Web Browser SSO</para> + </listitem> + <listitem> + <para>Single Logout</para> + </listitem> </itemizedlist> <itemizedlist> <title>Available SAML 2.0 Bindings</title> - <listitem><para>HTTP Post Binding</para></listitem> - <listitem><para>HTTP Redirect</para></listitem> + <listitem> + <para>HTTP Post Binding</para> + </listitem> + <listitem> + <para>HTTP Redirect</para> + </listitem> </itemizedlist> <para> - JBoss Portal Platform 6 Beta can act either as an Identity Provider or as a Service Provider. + JBoss Portal Platform 6 can act either as an Identity Provider or as a Service Provider. </para> <note> <para>SAML 2.0 authentication is not available for Web Services Remote Portlets (WSRP).</para> @@ -36,7 +43,7 @@ </section> <section> <title>Apache CXF for WSRP</title> - <para>JBoss Portal Platform 6 Beta uses the Apache CXF framework for Web Services.</para> + <para>JBoss Portal Platform 6 uses the Apache CXF framework for Web Services.</para> </section> <section> <title>User Interface</title> @@ -44,5 +51,4 @@ The administration interface and tooling are mostly unchanged from JBoss Enterprise Portal Platform 5. Minimal differences may appear. </para> </section> - </chapter> Modified: epp/docs/branches/6.0/Release_Notes/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/Revision_History.xml 2013-03-01 05:49:11 UTC (rev 9190) +++ epp/docs/branches/6.0/Release_Notes/en-US/Revision_History.xml 2013-03-01 06:46:33 UTC (rev 9191) @@ -6,7 +6,7 @@ <simpara> <revhistory> <revision> - <revnumber>6.0.0-10</revnumber> + <revnumber>6.0.0-12</revnumber> <date>Fri Mar 01 2013</date> <author> <firstname>Jared</firstname>

11 years, 2 months

1
0
0 / 0

gatein SVN: r9190 - epp/docs/branches/6.0/Release_Notes/en-US.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2013-03-01 00:49:11 -0500 (Fri, 01 Mar 2013) New Revision: 9190 Removed: epp/docs/branches/6.0/Release_Notes/en-US/Resolved_Issues.xml Log: Release Note draft content as extracted from DocDash Deleted: epp/docs/branches/6.0/Release_Notes/en-US/Resolved_Issues.xml ===================================================================

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-commits March 2013