February 2013 - gatein-commits - Jboss List Archives

gatein SVN: r9188 - epp/docs/branches/6.0/Developer_Guide/en-US.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2013-02-27 22:47:52 -0500 (Wed, 27 Feb 2013) New Revision: 9188 Modified: 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: BZ#856447 - Amended the link with the verbatim one Filip provided. Verified it resolved when clicked. 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-02-27 12:16:44 UTC (rev 9187) +++ epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml 2013-02-28 03:47:52 UTC (rev 9188) @@ -4,8 +4,8 @@ <title>Revision History</title> <simpara> <revhistory> - <revision> - <revnumber>6.0.0-19</revnumber> + <revision> + <revnumber>6.0.0-20</revnumber> <date>Fri Feb 27 2013</date> <author> <firstname>Aakanksha</firstname> @@ -18,7 +18,7 @@ </simplelist> </revdescription> </revision> - <revision> + <revision> <revnumber>6.0.0-18</revnumber> <date>Fri Feb 21 2013</date> <author> @@ -28,7 +28,7 @@ </author> <revdescription> <simplelist> - <member>BZ#912678: NEEDINFO - Incorporating SME feedback</member> + <member>BZ#912678: NEEDINFO - Incorporating SME feedback</member> </simplelist> </revdescription> </revision> @@ -42,7 +42,7 @@ </author> <revdescription> <simplelist> - <member>Re-added 'Quickstarts' appendix to the book.</member> + <member>Re-added 'Quickstarts' appendix to the book.</member> </simplelist> </revdescription> </revision> 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-02-27 12:16:44 UTC (rev 9187) +++ epp/docs/branches/6.0/Developer_Guide/en-US/appendix-Quickstarts.xml 2013-02-28 03:47:52 UTC (rev 9188) @@ -1,75 +1,69 @@ -<?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"> +<?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="Appendix_-_Quickstarts"> - - <title>Appendix - Quickstarts</title> - <para>JBoss Portal Platform Quickstarts provide small, specific, working examples that can be used as a reference for your own project.</para> - <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> - <itemizedlist> - <listitem> - <para> - A zip archive containing all Quickstarts can be downloaded from the <ulink url="https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl...">JBoss Portal Platform Downloads page</ulink> on Customer Portal</para> - </listitem> - </itemizedlist> -<note> -<para> -For information on using WOLF repo refer to the <filename>readme</filename> file avaiable in the quickstarts. + <title>Appendix - Quickstarts</title> + <para>JBoss Portal Platform Quickstarts provide small, specific, working examples that can be used as a reference for your own project.</para> + <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> + <note> + <para> +For information on using the WOLF repository, see the <filename>readme</filename> file packaged with the quickstarts. </para> -</note> - </section> - <section id="JBoss_Developer_Studio_or_Eclipse_with_JBoss_Tools"> - - <title>JBoss Developer Studio or Eclipse with JBoss Tools</title> - <itemizedlist> - <listitem> - <para> + </note> + </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> + <para> In your Workbench, go to <code>File > New > Example... > JBoss Tools > Project Examples</code> </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> 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> + </listitem> + <listitem> + <para> Select one of the available Quickstarts, e.g. <code>Simplest Hello World Portlet</code> </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> Click <code>Finish</code> and the example project will be imported into your workspace. </para> - </listitem> - </itemizedlist> -<note> -<para> -For more information on how to use and deploy quickstarts, refer to the <filename>readme</filename> file of the quickstart. + </listitem> + </itemizedlist> + <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. </para> -</note> -  - </section> -  </section> + - </chapter> + </section> --></chapter>

11 years, 1 month

1
0
0 / 0

gatein SVN: r9187 - epp/docs/branches/6.0/Developer_Guide/en-US.

by do-not-reply＠jboss.org

Author: aakanksha_writer Date: 2013-02-27 07:16:44 -0500 (Wed, 27 Feb 2013) New Revision: 9187 Modified: 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: link to quickstart updated 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-02-27 05:01:13 UTC (rev 9186) +++ epp/docs/branches/6.0/Developer_Guide/en-US/Revision_History.xml 2013-02-27 12:16:44 UTC (rev 9187) @@ -5,6 +5,20 @@ <simpara> <revhistory> <revision> + <revnumber>6.0.0-19</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> 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-02-27 05:01:13 UTC (rev 9186) +++ epp/docs/branches/6.0/Developer_Guide/en-US/appendix-Quickstarts.xml 2013-02-27 12:16:44 UTC (rev 9187) @@ -3,7 +3,6 @@ <chapter id="Appendix_-_Quickstarts"> <title>Appendix - Quickstarts</title> - <remark>BZ#912678: NEEDINFO -Awaiting inputs from Honza on how to use WOLF repository which is needed to build ent.quickstarts</remark> <para>JBoss Portal Platform Quickstarts provide small, specific, working examples that can be used as a reference for your own project.</para> <para>The Quickstarts can be obtained in one of the following ways:</para> <section id="JBoss_Portal_Platform_Downloads_Page"> @@ -12,14 +11,18 @@ <itemizedlist> <listitem> <para> - A zip archive containing all Quickstarts can be downloaded from the <ulink url="https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl...">JBoss Portal Platform Downloads page</ulink> on Customer Portal</para> + A zip archive containing all Quickstarts can be downloaded from the <ulink url="https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downl...">JBoss Portal Platform Downloads page</ulink> on Customer Portal</para> </listitem> </itemizedlist> +<note> +<para> +For information on using WOLF repo refer to the <filename>readme</filename> file avaiable in the quickstarts. +</para> +</note> </section> <section id="JBoss_Developer_Studio_or_Eclipse_with_JBoss_Tools"> <title>JBoss Developer Studio or Eclipse with JBoss Tools</title> - <remark>BZ#912678:NEEDINFO -Complete information needed on how to deploy quickstarts directly from IDE to JPP </remark> <itemizedlist> <listitem> <para> @@ -48,6 +51,11 @@ </para> </listitem> </itemizedlist> +<note> +<para> +For more information on how to use and deploy quickstarts, refer to the <filename>readme</filename> file of the quickstart. +</para> +</note> <!-- <para> The new runtime environment allows to deploy quickstarts directly from IDE to JBoss Portal Platform. </para>

11 years, 1 month

1
0
0 / 0

gatein SVN: r9186 - in epp/docs/branches/6.0/Reference_Guide/en-US: images/PortalDevelopment/Skinning and 2 other directories.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2013-02-27 00:01:13 -0500 (Wed, 27 Feb 2013) New Revision: 9186 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Reference_Guide/en-US/images/PortalDevelopment/Skinning/portal-change-skin.png 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 epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml Log: BZ#912678 - incorporated all observations from QE. BZ#913291 - changed file paths to match the Confluence paths. 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-02-27 02:09:48 UTC (rev 9185) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-02-27 05:01:13 UTC (rev 9186) @@ -7,25 +7,53 @@ <title>Revision History</title> <simpara> <revhistory> - <revision> - <revnumber>6.0.0-51</revnumber> - <date>Tue Feb 26 2013</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></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-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> + </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> @@ -77,7 +105,7 @@ </author> <revdescription> <simplelist> - <member>BZ#907672 - Incorporated "Upload Component" content from Confluence wiki, up to version 3.</member> + <member>BZ#907672 - Incorporated "Upload Component" content from Confluence wiki, up to version 3.</member> </simplelist> </revdescription> </revision> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/images/PortalDevelopment/Skinning/portal-change-skin.png =================================================================== (Binary files differ) 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-02-27 02:09:48 UTC (rev 9185) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationAuthorizationOverview.xml 2013-02-27 05:01:13 UTC (rev 9186) @@ -85,17 +85,17 @@ </login-config> </programlisting> <para> <literal>LoginServlet</literal> redirects the user to the login page placed in <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/login/jsp/login.jsp</filename>. - <figure> - <title>Default Login Form on the login.jsp Page</title> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/AuthenticationAndIdentity/Overview/loginScreen.png" format="PNG"/> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" scalefit="1" fileref="images/AuthenticationAndIdentity/Overview/loginScreen.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Default Login Form on the login.jsp Page</title> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/AuthenticationAndIdentity/Overview/loginScreen.png" format="PNG"/> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" scalefit="1" fileref="images/AuthenticationAndIdentity/Overview/loginScreen.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> </para> <para> 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>. @@ -110,7 +110,7 @@ <section id="sect-Authentication_Authorization_Intro-Login_Modules"> <title>Login Modules</title> <para> -From the WCI servlet API login, the user is redirected to JAAS authentication. JBoss Portal Platform uses its own security domain (<emphasis role="bold">gatein-domain</emphasis>) with a set of predefined login modules. Login module configuration for <emphasis>gatein-domain</emphasis> is contained in the <filename>JPP_HOME/gatein/gatein.ear/META-INF/gatein-jboss-beans.xml</filename> file. +From the WCI servlet API login, the user is redirected to JAAS authentication. JBoss Portal Platform uses its own security domain (<emphasis role="bold">gatein-domain</emphasis>) with a set of predefined login modules. Login module configuration for <emphasis>gatein-domain</emphasis> is contained in the <filename>JPP_HOME/standalone/configuration/standalone.xml</filename> file. </para> <para> Below is the default login modules stack: @@ -136,7 +136,7 @@ New login modules can be added or the stack completely replaced with custom modules. </para> <para> - Authentication starts with the login method of each login module being invoked. After all login methods are invoked, the authentication is continued by invoking the commit method on each login module. Both login and commit methods can throw LoginException. If it happens, then the whole authentication ends unsuccessfully, which in turn invokes the abort method on each login module. By returning "false" from the login method, you can ensure that the login module is ignored. This is not specific to JBoss Portal Platform but it is generic to JAAS. Refer to <ulink url="http://docs.oracle.com/javase/6/docs/technotes/guides/security/jaas/JAASR..." type="http">http://docs.oracle.com/javase/6/docs/technotes/guides/security/jaas/JAASR...</ulink> here for more information about login modules in general. + Authentication starts with the login method of each login module being invoked. After all login methods are invoked, the authentication is continued by invoking the commit method on each login module. Both login and commit methods can throw LoginException. If it happens, then the whole authentication ends unsuccessfully, which in turn invokes the abort method on each login module. By returning "false" from the login method, you can ensure that the login module is ignored. This is not specific to JBoss Portal Platform but it is generic to JAAS. See <ulink url="http://docs.oracle.com/javase/6/docs/technotes/guides/security/jaas/JAASR..." type="http"/> for more information about login modules in general. </para> <section id="sect-Authentication_Authorization_Intro-existingLM"> <title>Existing Login Modules</title> @@ -157,7 +157,8 @@ <term>JBoss Enterprise Application Platform 6 LoginModule</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. 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 t! o 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 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. </para> </listitem> </varlistentry> @@ -350,15 +351,34 @@ <para> Default implementation <emphasis>DefaultRolesExtractorImpl</emphasis> is based on a special algorithm, which uses the name of the role from the root of the group (for example for role "/organization/management/something" we have JAAS role "organization"). The only exception is the "platform" group where we use second level as the name of the group. For example from group "/platform/users" we have JAAS role "users". </para> - <para> - <emphasis role="bold">Example: </emphasis> We have user <emphasis>root</emphasis>, which has memberships <emphasis>member:/platform/users</emphasis>, <emphasis>manager:/platform/administrators</emphasis>, <emphasis>validator:/platform/managers</emphasis>, <emphasis>member:/partners</emphasis>, <emphasis>member:/customers/acme</emphasis>, <emphasis>member:/organization/management/board</emphasis>. In this case we will have JAAS roles: <emphasis>users</emphasis>, <emphasis>administrators</emphasis>, <emphasis>managers</emphasis>, <emphasis>partners</emphasis>, <emphasis>customers</emphasis>, <emphasis>organization</emphasis>. + <para>For example, the user root has the following memberships:</para> + <itemizedlist> + <listitem> + <para>member:/platform/users</para> + </listitem> + <listitem> + <para>manager:/platform/administrators</para> + </listitem> + <listitem> + <para>validator:/platform/managers</para> + </listitem> + <listitem> + <para>member:/partners</para> + </listitem> + <listitem> + <para>member:/customers/acme</para> + </listitem> + <listitem> + <para>member:/organization/management/board</para> + </listitem> + </itemizedlist> + <para>In this case we will have JAAS roles: users, administrators, managers, partners, customers, organization. </para> - <para> - Default implementation of Authenticator is <emphasis>OrganizationAuthenticatorImpl</emphasis>, which is implementation based on <emphasis>OrganizationService</emphasis>. See <xref linkend="sect-Reference_Guide-Organization_API"/> . + <para>The default implementation of Authenticator is <emphasis>OrganizationAuthenticatorImpl</emphasis>, which is implementation based on <emphasis>OrganizationService</emphasis>. See <xref linkend="sect-Reference_Guide-Organization_API"/> . </para> <para> You can override the default implementation of the mentioned <systemitem>Authenticator</systemitem> and <systemitem>RolesExtractor</systemitem> interfaces if the default behavior is not suitable for your needs. - </para> + </para> </section>  </section>  <section id="sect-Authentication_Authorization_Intro-differentAuthWorkflows"> @@ -403,7 +423,7 @@ </listitem> <listitem> <para> - There is a special HTTP Filter <emphasis role="bold">RememberMeFilter</emphasis> configured in web.xml, which checks the RememberMe cookie and then it retrieves credentials of user from RemindPasswordTokenService. Now filter redirects request to PortalLoginController and authentication process goes in same way as for normal FORM based authentication. + There is a special HTTP Filter RememberMeFilter configured in <filename>web.xml</filename>, which checks the RememberMe cookie and then it retrieves credentials of user from RemindPasswordTokenService. Now filter redirects request to PortalLoginController and authentication process goes in same way as for normal FORM based authentication. </para> </listitem> </itemizedlist> @@ -411,11 +431,9 @@ <section id="sect-Authentication_Authorization_Intro-RememberMeAuthentication-RemindPasswordTokenService"> <title>RemindPasswordTokenService</title> <para> - This is a special service used during the RememberMe authentication workflow. It is configurable in the file <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/conf/common/remindpwd-configuration.xml</filename> . For more info, look at section <xref linkend="sect-Reference_Guide-Authentication_Token_Configuration"/> - </para> + This is a special service used during the RememberMe authentication workflow. It is configurable in the file <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/conf/common/remindpwd-configuration.xml</filename> . See <xref linkend="sect-Reference_Guide-Authentication_Token_Configuration"/> for more information. </para> <para> - You can encrypt passwords before storing them in JCR. More info is in section <xref linkend="sect-Reference_Guide-Authentication_and_Identity-Password_Encryption"/>. - </para> + You can encrypt passwords before storing them in JCR. See <xref linkend="sect-Reference_Guide-Authentication_and_Identity-Password_Encryption"/> for more information. </para> </section> </section> <section id="sect-Authentication_Authorization_Intro-authorization"> 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-02-27 02:09:48 UTC (rev 9185) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PasswordEncryption.xml 2013-02-27 05:01:13 UTC (rev 9186) @@ -7,11 +7,11 @@ <title>Password Encryption</title> <section id="sid-54264610_PasswordEncryption-HashingandsaltingofpasswordsinPicketlinkIDM"> <title>Hashing and Salting of Passwords in PicketLink IDM</title> -<remark>Source: https://docs.jboss.org/author/display/GTNPORTAL35/Password+Encryption</remark> + <remark>Source: https://docs.jboss.org/author/display/GTNPORTAL35/Password+Encryption</remark> <para> -JBoss Portal Platform is using the +JBoss Portal Platform uses <ulink url="http://www.jboss.org/picketlink/IDM">PicketLink IDM</ulink> - framework to store information about identity objects (users/groups/memberships). For better security, PicketLink IDM does not save user passwords into database in plain-text, but it uses <code>CredentialEncoder</code>, which encode password and save the encoded form into PicketLink IDM database. Later when user want to authenticate, they need to provide their password in plain-text via a web login form. The provided password is then encoded and compared to an encoded password in the PicketLink IDM database. JBoss Portal Platform is then able to authenticate user based on this comparison. More information can be found in <xref linkend="sect-Reference_Guide-PicketLink_IDM_integration"/>. + framework to store information about identity objects (users/groups/memberships). For better security, PicketLink IDM does not save user passwords into database in plain-text, but it uses <code>CredentialEncoder</code>, which encodes password and saves the encoded form into PicketLink IDM database. Later when the user wants to authenticate, they need to provide their password in plain-text through a web login form. The provided password is then encoded and compared to an encoded password in the PicketLink IDM database. JBoss Portal Platform is then able to authenticate the user based on this comparison. See <xref linkend="sect-Reference_Guide-PicketLink_IDM_integration"/> for more information. </para> <para> Default implementation of @@ -23,7 +23,7 @@ <title>Choosing CredentialEncoder Implementation</title> <para> The implementation of CredentialEncoder is configured in file - <code>GATEIN_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml</code> + <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 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2013-02-27 02:09:48 UTC (rev 9185) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2013-02-27 05:01:13 UTC (rev 9186) @@ -560,13 +560,13 @@ <section id="sect-Reference_Guide-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project"> <title><remark>BZ#856430</remark>Java Open Single Sign-On (JOSSO)</title> <para> - Java Open Single Sign-On (JOSSO) is an open-source single sign-on solution based on Java EE. It allows multiple web servers or web applications to authenticate users with a credential store. Detailed information about JOSSO can be found at <ulink url="http://www.josso.org"/>. - </para> - <para> + Java Open Single Sign-On (JOSSO) is an open-source single sign-on solution based on Java EE. It allows multiple web servers or web applications to authenticate users with a credential store. Detailed information about JOSSO can be found at <ulink url="http://www.josso.org"/>. + </para> + <para> JOSSO integration with JBoss Portal Platform requires an Apache Tomcat server instance to host JOSSO. JBoss Portal Platform communicates with the JOSSO server through a single sign-on plug-in. - </para> - <para> - Setting up the integration consists of two steps – setting up the JOSSO server and setting up the portal to use the JOSSO server. These two steps differ depending on the used version of JOSSO, as described in <xref linkend="sect-JOSSO-1.8" /> and <xref linkend="sect-JOSSO-2.2" />. After completing the procedures described in either section, all links redirecting to user authentication pages will redirect to the JOSSO centralized authentication form. + </para> + <para> + Setting up the integration consists of two steps – setting up the JOSSO server and setting up the portal to use the JOSSO server. These two steps differ depending on the used version of JOSSO, as described in <xref linkend="sect-JOSSO-1.8"/> and <xref linkend="sect-JOSSO-2.2"/>. After completing the procedures described in either section, all links redirecting to user authentication pages will redirect to the JOSSO centralized authentication form. </para> <section id="sect-Reference_Guide-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project-Auth_Process"> <title>Authentication Process</title> @@ -615,32 +615,32 @@ <para> <emphasis role="bold">Optional:</emphasis> To use the SSO authentication plug-in with JOSSO (not mandatory but recommended, see <xref linkend="sect-Reference_Guide-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project-Auth_Process"/> for details), copy the contents of the <filename>JPP_DIST/gatein-sso/josso/josso-<replaceable><version></replaceable>/plugin/</filename> directory into the <replaceable>JOSSO_HOME</replaceable> directory. Among the files that will be copied, the following ones are the most important: </para> - <itemizedlist> - <listitem> - <para> + <itemizedlist> + <listitem> + <para> <filename><replaceable>JOSSO_HOME</replaceable>/lib/josso-gateway-config.xml</filename> - </para> - <para> - The original file is being replaced. You should consider creating a backup of it before adding the new file. + </para> + <para> + The original file is being replaced. You should consider creating a backup of it before adding the new file. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> <filename><replaceable>JOSSO_HOME</replaceable>/lib/josso-gateway-gatein-stores.xml</filename> - </para> - <para> - This file is not present in the original <replaceable>JOSSO_HOME</replaceable> download. + </para> + <para> + This file is not present in the original <replaceable>JOSSO_HOME</replaceable> download. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> <filename>JOSSO_HOME/webapps/josso/WEB-INF/classes/gatein.properties</filename> - </para> - <para> - This file is not present in the original <replaceable>JOSSO_HOME</replaceable> download. You may need to edit the file and change the host and port to match your JBoss Portal Platform instance. The values will be used by the authentication plug-in when sending REST requests over HTTP. + </para> + <para> + This file is not present in the original <replaceable>JOSSO_HOME</replaceable> download. You may need to edit the file and change the host and port to match your JBoss Portal Platform instance. The values will be used by the authentication plug-in when sending REST requests over HTTP. </para> - </listitem> - </itemizedlist> + </listitem> + </itemizedlist> </step> <step> <para> @@ -958,20 +958,20 @@ </substeps> </step> <step> - <para>Test the configuration:</para> + <para>Test the configuration:</para> <substeps> <step> <para> Start the Portal. </para> - </step> - <step> + </step> + <step> <para> Access <uri>http://localhost:8080/portal</uri> and click <emphasis role="italics">Sign in</emphasis>. You will be redirected to the JOSSO instance, but you will need to login with the username and password created via the JOSSO console (for example <literal>john</literal>/<literal>password</literal>) as REST callbacks are not supported. </para> </step> </substeps> - <para>After a successful login to JOSSO, you will be redirected to the portal authenticated as <literal>john</literal>.</para> + <para>After a successful login to JOSSO, you will be redirected to the portal authenticated as <literal>john</literal>.</para> </step> </procedure> </section> @@ -1658,7 +1658,7 @@ <term>gatein.sso.filter.login.sso.url</term> <listitem> <para> - This value ensures that clicking the <guibutton>Sign in</guibutton> link will redirect users to the <literal>/portal/dologin</literal> URL, which is a secured URL declared in the <filename>security-constraint section of JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename> file, allowing the <systemitem>GateInNegotiationAuthenticator</systemitem> valve to intercept the HTTP request. + This value ensures that clicking the <guibutton>Sign in</guibutton> link will redirect users to the <literal>/portal/dologin</literal> URL, which is a secured URL declared in the <security-constraint> section of <filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename> file, allowing the <systemitem>GateInNegotiationAuthenticator</systemitem> valve to intercept the HTTP request. </para> </listitem> </varlistentry> @@ -1871,9 +1871,9 @@ </para> <procedure id="proc-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Testing_the_SSO_Valve"> <title>Configuring and Testing Single-Sign On in a Shared DNS Domain</title> - <para> + <para> This procedure demonstrates the configuration and testing of single sign-on for two JBoss Portal Platform server instances running in a shared domain on a single physical Linux machine.</para> - <para>It is expected that each instance is installed in a separate directory in the machine's file system, and that the <literal>192.168.210.101</literal> and <literal>192.168.210.102</literal> virtual IP addresses are available on the machine. + <para>It is expected that each instance is installed in a separate directory in the machine's file system, and that the <literal>192.168.210.101</literal> and <literal>192.168.210.102</literal> virtual IP addresses are available on the machine. </para> <step> <para> @@ -1894,7 +1894,7 @@ </step> <step> <para>By default, the <filename>standalone-ha.xml</filename> file is configured to use a shared H2 database, which is intended to be used only for testing purposes. Start the database by issuing the following command in the <replaceable>JPP_HOME</replaceable> directory of the first instance:</para> -<programlisting> + <programlisting> java -cp modules/com/h2database/h2/main/h2-<replaceable><VERSION></replaceable>.jar org.h2.tools.Server </programlisting> </step> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml 2013-02-27 02:09:48 UTC (rev 9185) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml 2013-02-27 05:01:13 UTC (rev 9186) @@ -159,7 +159,7 @@ <taskrelated> <note> <para> - Disabling the default <emphasis>portal</emphasis> container is possible as well, but some functions, such as WSRP, or Services Management, depend on the default portal container to be deployed, and will no longer work if this is disabled. + Disabling the default portal container is possible, but not recommended. Some functions, such as WSRP or Services Management, depend on the default portal container to be deployed. These functions will no longer work if the default portal container is disabled. </para> </note> </taskrelated> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2013-02-27 02:09:48 UTC (rev 9185) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2013-02-27 05:01:13 UTC (rev 9186) @@ -29,7 +29,7 @@ </listitem> </itemizedlist> <para> - These navigators are configured using the standard XML syntax in the file: <filename>portal.war/WEB-INF/conf/portal/portal-configuration.xml</filename>. + These navigators are configured using the standard XML syntax in the file: <filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/portal/portal-configuration.xml</filename>. </para> <programlisting language="XML" role="XML"><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../extras/PortalDevelopment_DefaultPortalNavigationConfiguration/default144.xml" parse="text"/></programlisting> <para> @@ -171,7 +171,7 @@ <term>pages.xml</term> <listitem> <para> - This configuration file structure is very similar to <filename>portal.xml</filename> and it can also contain container tags (some usage examples of container tags can be found in <filename>portal.war/WEB-INF/conf/portal/portal/sharedlayout.xml</filename>). + This configuration file structure is very similar to <filename>portal.xml</filename> and it can also contain container tags (some usage examples of container tags can be found in <filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/portal/portal/sharedlayout.xml</filename>). </para> <para> Each application can decide whether to render the portlet border, the window state, the icons, or the portlet mode. @@ -189,7 +189,7 @@ The group navigation menu is configured by two XML files (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). The syntax used in these files is the same as those covered in <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation"/>. </para> <para> - They are located in <filename>portal.war/WEB-INF/conf/portal/group<replaceable>/group-name-path/</replaceable></filename> directory (For example; <filename>portal.war/WEB-INF/conf/portal/group/platform/administrators/</filename>). + They are located in <filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/portal/group<replaceable>/group-name-path/</replaceable></filename> directory (For example; <filename>portal.war/WEB-INF/conf/portal/group/platform/administrators/</filename>). </para> </section> <section id="sect-Reference_Guide-Portal_Navigation_Configuration-User_Navigation"> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml 2013-02-27 02:09:48 UTC (rev 9185) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml 2013-02-27 05:01:13 UTC (rev 9186) @@ -59,7 +59,7 @@ Various languages are available in the portal package. The configuration below will define which languages are shown in the "<emphasis role="bold">Change Language</emphasis>" section and made available to users. </para> <para> - The <filename>portal.war:/WEB-INF/conf/common/common-configuration.xml</filename> file of your installation contains the following section: + The <filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/common/common-configuration.xml</filename> file of your installation contains the following section: </para> <programlisting language="XML" role="XML"><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../extras/PortalDevelopment_InternationalizationConfiguration/default149.xml" parse="text"/></programlisting> <para> @@ -92,7 +92,7 @@ <title>ResourceBundleService</title> <remark>Source: https://docs.jboss.org/author/display/GTNPORTAL35/Internationalization+Co...</remark> <para> - The resource bundle service is configured in: <filename>portal.war:/WEB-INF/conf/common/common-configuration.xml</filename>: + The resource bundle service is configured in: <filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/conf/common/common-configuration.xml</filename>: </para> <example id="exam-common_config_xml_file_explained"> <title>The common-configuration.xml file explained</title> @@ -115,7 +115,7 @@ <para><xref linkend="exam-common_config_xml_file_explained"/> shows bundle definitions for the navigation of the classic portal and of four different groups. Each of these resource bundles occupies a different sphere, they are independent of each other and they are not included in the <parameter>portal.resource.names</parameter> parameter. </para> <para> - The properties for a group must be in the <filename>WEB-INF/classes/locale/navigation/group/</filename> folder. For example, <literal>/WEB-INF/classes/locale/navigation/group/organization/management/executive-board_en.properties</literal>. + The properties for a group must be in the <filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/classes/locale/navigation/group/</filename> folder. For example, <literal>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/classes/locale/navigation/group/organization/management/executive-board_en.properties</literal>. </para> <para> The folder and file names must correspond to the group hierarchy. The group name "<parameter>executive-board</parameter>" is followed by the ISO 639 code. @@ -144,7 +144,7 @@ <title>Add Spanish Translation to the GadgetPortlet</title> <step> <para> - Create the file <literal>GadgetPortlet_es.properties</literal> in <filename>WEB-INF/classes/locale/portlet/gadget/GadgetPortlet</filename>. + Create the file <literal>GadgetPortlet_es.properties</literal> in <filename>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/classes/locale/portlet/gadget/GadgetPortlet</filename>. </para> </step> <step> @@ -226,7 +226,7 @@ <title>Overriding Default JDK API Language Values</title> <step> <para>Edit the - <code>gatein.ear/portal.war/WEB-INF/classes/locale/portal/webui_<replaceable>xx_yy</replaceable>.properties</code> + <code>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/classes/locale/portal/webui_<replaceable>xx_yy</replaceable>.properties</code> file where <replaceable role="italics">xx_yy</replaceable> represents the country code of the language you wish to translate. </para> @@ -239,7 +239,7 @@ </step> <step> <para>Edit - <code>gatein.ear/portal.war/WEB-INF/classes/locale/portal/webui_fr.properties</code> + <code>JPP_HOME/gatein/gatein.ear/portal.war/WEB-INF/classes/locale/portal/webui_fr.properties</code> where <emphasis role="italics">fr</emphasis> is the country code for French, and add the following key into it: Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml 2013-02-27 02:09:48 UTC (rev 9185) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml 2013-02-27 05:01:13 UTC (rev 9186) @@ -252,7 +252,7 @@ That way even localization of servlets, and .jsps accessed in a non-bridged manner can stay in sync with portlet localization. </para> <para> - <literal>LocalizationFilter</literal> is installed through the portal's web.xml file: <filename><replaceable>JPP_DIST</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename>. + <literal>LocalizationFilter</literal> is installed through the portal's web.xml file: <filename><replaceable>JPP_HOME</replaceable>/gatein/gatein.ear/portal.war/WEB-INF/web.xml</filename>. </para> <programlisting language="XML" role="XML"><filter> <filter-name>LocalizationFilter</filter-name> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2013-02-27 02:09:48 UTC (rev 9185) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2013-02-27 05:01:13 UTC (rev 9186) @@ -248,9 +248,6 @@ <imageobject role="html"> <imagedata width="444" align="center" scale="100" fileref="images/PortalDevelopment/Skinning/portal-change-skin.png" format="PNG"/> </imageobject> - <imageobject role="fo"> - <imagedata width="444" contentwidth="150mm" align="center" fileref="images/PortalDevelopment/Skinning/portal-change-skin.png" format="PNG"/> - </imageobject> </mediaobject> </figure> <para>

11 years, 1 month

1
0
0 / 0

gatein SVN: r9185 - epp/docs/branches/6.0/User_Guide/en-US.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2013-02-26 21:09:48 -0500 (Tue, 26 Feb 2013) New Revision: 9185 Modified: epp/docs/branches/6.0/User_Guide/en-US/Author_Group.xml epp/docs/branches/6.0/User_Guide/en-US/Revision_History.xml Log: Changed the <editor> tag to <author> tag, so the book would build Modified: epp/docs/branches/6.0/User_Guide/en-US/Author_Group.xml =================================================================== --- epp/docs/branches/6.0/User_Guide/en-US/Author_Group.xml 2013-02-27 01:39:48 UTC (rev 9184) +++ epp/docs/branches/6.0/User_Guide/en-US/Author_Group.xml 2013-02-27 02:09:48 UTC (rev 9185) @@ -4,10 +4,10 @@ %BOOK_ENTITIES; ]> <authorgroup> - <editor> + <author> <firstname>Red Hat</firstname> <surname>Documentation Group</surname> - </editor> + </author> <othercredit> <affiliation> <orgname><emphasis role="bold"> 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-02-27 01:39:48 UTC (rev 9184) +++ epp/docs/branches/6.0/User_Guide/en-US/Revision_History.xml 2013-02-27 02:09:48 UTC (rev 9185) @@ -7,21 +7,21 @@ <title>Revision History</title> <simpara> <revhistory> - <revision> - <revnumber>6.0.0-12</revnumber> - <date>Wed Feb 27 2013</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - </author> - <revdescription> - <simplelist> - <member>BZ#856442: Updated screenshots for new product name and skin colors.</member> - </simplelist> - </revdescription> - </revision> - <revision> + <revision> + <revnumber>6.0.0-14</revnumber> + <date>Wed Feb 27 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> @@ -34,7 +34,7 @@ <member>BZ#856445 - Updated topic supported browsers</member> </simplelist> </revdescription> - </revision> + </revision> <revision> <revnumber>6.0.0-10</revnumber> <date>Wed Jan 23 2013</date> @@ -48,78 +48,78 @@ <member>BZ#886376 - Updated all Book_Info.xml files with consistent subtitle. Rebuilt for review..</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></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></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></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></email> - </author> - <revdescription> - <simplelist> - <member>BZ#856442: Removed numerous unnecessary images.</member> - </simplelist> - </revdescription> - </revision> + </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>

11 years, 1 month

1
0
0 / 0

gatein SVN: r9184 - epp/docs/branches/6.0/User_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2013-02-26 20:39:48 -0500 (Tue, 26 Feb 2013) New Revision: 9184 Modified: epp/docs/branches/6.0/User_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/User_Guide/en-US/User_Guide.xml Log: Added draft watermark and incremented for staging 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-02-27 01:06:53 UTC (rev 9183) +++ epp/docs/branches/6.0/User_Guide/en-US/Revision_History.xml 2013-02-27 01:39:48 UTC (rev 9184) @@ -7,7 +7,21 @@ <title>Revision History</title> <simpara> <revhistory> - <revision> + <revision> + <revnumber>6.0.0-12</revnumber> + <date>Wed Feb 27 2013</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></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> 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-02-27 01:06:53 UTC (rev 9183) +++ epp/docs/branches/6.0/User_Guide/en-US/User_Guide.xml 2013-02-27 01:39:48 UTC (rev 9184) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "User_Guide.ent"> %BOOK_ENTITIES; ]> -<book> +<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="modules/Introduction.xml"/>

11 years, 1 month

1
0
0 / 0

gatein SVN: r9183 - epp/docs/branches/6.0/User_Guide/en-US/images.

by do-not-reply＠jboss.org

Author: smumford Date: 2013-02-26 20:06:53 -0500 (Tue, 26 Feb 2013) New Revision: 9183 Modified: epp/docs/branches/6.0/User_Guide/en-US/images/ActivePortals.png epp/docs/branches/6.0/User_Guide/en-US/images/DashboardPortlet.png epp/docs/branches/6.0/User_Guide/en-US/images/EditorPortlet.png epp/docs/branches/6.0/User_Guide/en-US/images/GroupPortlet.png epp/docs/branches/6.0/User_Guide/en-US/images/HomePage2.png epp/docs/branches/6.0/User_Guide/en-US/images/Non-tech-docs.png epp/docs/branches/6.0/User_Guide/en-US/images/RSSReader.png epp/docs/branches/6.0/User_Guide/en-US/images/SitePortlet.png epp/docs/branches/6.0/User_Guide/en-US/images/StarPortlet.png Log: BZ#856442: Updated screenshots fornew name and skin colors Modified: epp/docs/branches/6.0/User_Guide/en-US/images/ActivePortals.png =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/User_Guide/en-US/images/DashboardPortlet.png =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/User_Guide/en-US/images/EditorPortlet.png =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/User_Guide/en-US/images/GroupPortlet.png =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/User_Guide/en-US/images/HomePage2.png =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/User_Guide/en-US/images/Non-tech-docs.png =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/User_Guide/en-US/images/RSSReader.png =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/User_Guide/en-US/images/SitePortlet.png =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/User_Guide/en-US/images/StarPortlet.png =================================================================== (Binary files differ)

11 years, 1 month

1
0
0 / 0

gatein SVN: r9182 - in epp/docs/branches/6.0/Reference_Guide/en-US: images/AuthenticationAndIdentity/SAML2 and 1 other directories.

by do-not-reply＠jboss.org

Author: smumford Date: 2013-02-26 00:28:17 -0500 (Tue, 26 Feb 2013) New Revision: 9182 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/6.0/Reference_Guide/en-US/images/AuthenticationAndIdentity/SAML2/saml-sso.png epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SAML2.xml Log: BZ#856430: Details in Comment 28 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-02-26 01:51:57 UTC (rev 9181) +++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-02-26 05:28:17 UTC (rev 9182) @@ -7,6 +7,24 @@ <title>Revision History</title> <simpara> <revhistory> + <revision> + <revnumber>6.0.0-51</revnumber> + <date>Tue Feb 26 2013</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></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> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/images/AuthenticationAndIdentity/SAML2/saml-sso.png =================================================================== (Binary files differ) Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SAML2.xml =================================================================== (Binary files differ)

11 years, 1 month

1
0
0 / 0

gatein SVN: r9181 - in epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584: gadgets/gwtGadgets and 2 other directories.

by do-not-reply＠jboss.org

Author: ghjboss Date: 2013-02-25 20:51:57 -0500 (Mon, 25 Feb 2013) New Revision: 9181 Added: epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/src/main/java/org/gatein/management/gadget/mop/exportimport/server/IdentityFilter.java Modified: epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/component/common/src/main/java/org/gatein/common/xml/stax/navigator/StaxNavUtils.java epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/pom.xml epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/src/main/webapp/WEB-INF/web.xml Log: commit the fix for BZ913125 and BZ913584 Modified: epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/component/common/src/main/java/org/gatein/common/xml/stax/navigator/StaxNavUtils.java =================================================================== --- epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/component/common/src/main/java/org/gatein/common/xml/stax/navigator/StaxNavUtils.java 2013-02-25 15:07:23 UTC (rev 9180) +++ epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/component/common/src/main/java/org/gatein/common/xml/stax/navigator/StaxNavUtils.java 2013-02-26 01:51:57 UTC (rev 9181) @@ -31,6 +31,8 @@ import org.staxnav.ValueType; import javax.xml.namespace.QName; +import javax.xml.stream.XMLInputFactory; + import java.io.InputStream; import java.io.Reader; import java.util.Arrays; @@ -190,7 +192,9 @@ private static StaxNavBuilder buildDefaultNavigator() { - return new StaxNavBuilderImpl(); + return new StaxNavBuilderImpl() + // Do not support external entities in XML documents. + .withProperty(XMLInputFactory.IS_SUPPORTING_EXTERNAL_ENTITIES, false); } private StaxNavUtils() {} Modified: epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/pom.xml =================================================================== --- epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/pom.xml 2013-02-25 15:07:23 UTC (rev 9180) +++ epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/pom.xml 2013-02-26 01:51:57 UTC (rev 9181) @@ -56,6 +56,11 @@ <artifactId>exo.kernel.container</artifactId> <scope>provided</scope> </dependency> + <dependency> + <groupId>org.exoplatform.core</groupId> + <artifactId>exo.core.component.security.core</artifactId> + <scope>provided</scope> + </dependency>  <dependency> <groupId>com.google.gwt</groupId> Added: epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/src/main/java/org/gatein/management/gadget/mop/exportimport/server/IdentityFilter.java =================================================================== --- epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/src/main/java/org/gatein/management/gadget/mop/exportimport/server/IdentityFilter.java (rev 0) +++ epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/src/main/java/org/gatein/management/gadget/mop/exportimport/server/IdentityFilter.java 2013-02-26 01:51:57 UTC (rev 9181) @@ -0,0 +1,165 @@ +/* + * JBoss, Home of Professional Open Source. + * Copyright 2012, Red Hat, Inc., and individual contributors + * as indicated by the @author tags. See the copyright.txt file in the + * distribution for a full listing of individual contributors. + * + * This is free software; you can redistribute it and/or modify it + * under the terms of the GNU Lesser General Public License as + * published by the Free Software Foundation; either version 2.1 of + * the License, or (at your option) any later version. + * + * This software is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a copy of the GNU Lesser General Public + * License along with this software; if not, write to the Free + * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA + * 02110-1301 USA, or see the FSF site: http://www.fsf.org. + */ + +package org.gatein.management.gadget.mop.exportimport.server; + +import org.exoplatform.container.ExoContainer; +import org.exoplatform.container.web.AbstractFilter; +import org.exoplatform.services.security.ConversationRegistry; +import org.exoplatform.services.security.ConversationState; +import org.exoplatform.services.security.Identity; +import org.exoplatform.services.security.StateKey; +import org.exoplatform.services.security.web.HttpSessionStateKey; +import org.gatein.common.logging.Logger; +import org.gatein.common.logging.LoggerFactory; + +import javax.servlet.Filter; +import javax.servlet.FilterChain; +import javax.servlet.FilterConfig; +import javax.servlet.ServletException; +import javax.servlet.ServletRequest; +import javax.servlet.ServletResponse; +import javax.servlet.http.HttpServletRequest; +import javax.servlet.http.HttpServletResponse; +import javax.servlet.http.HttpSession; +import java.io.IOException; +import java.io.Writer; + +/** + * Identity filter which checks to see if an identity from the portal can be found before processing request. + * + * @author <a href="mailto:nscavell@redhat.com">Nick Scavelli</a> + */ +public class IdentityFilter extends AbstractFilter implements Filter +{ + + private static final Logger log = LoggerFactory.getLogger(IdentityFilter.class); + + private String role; + private String group; + private String user; + + @Override + protected void afterInit(FilterConfig config) throws ServletException + { + role = config.getInitParameter("role"); + group = config.getInitParameter("group"); + user = config.getInitParameter("user"); + } + + @Override + public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException + { + HttpServletRequest httpRequest = (HttpServletRequest) request; + HttpServletResponse httpResponse = (HttpServletResponse) response; + + HttpSession httpSession = httpRequest.getSession(); + StateKey stateKey = new HttpSessionStateKey(httpSession); + + ExoContainer container = getContainer(); + + ConversationRegistry conversationRegistry = + (ConversationRegistry) container.getComponentInstanceOfType(ConversationRegistry.class); + + ConversationState state = conversationRegistry.getState(stateKey); + if (state == null) + { + log.error("Conversation state not found. This typically means the GWT Gadget application is either being access anonymously or from outside the portal."); + handleError(httpRequest, httpResponse, 401); + return; + } + Identity identity = state.getIdentity(); + if (identity == null) + { + log.error("Identity not found from conversation state. This should not happen. GWT Gadget will not process"); + handleError(httpRequest, httpResponse, 401); + return; + } + ConversationState.setCurrent(state); + + // Do not process if nothing was configured + if (role == null && group == null && user == null) + { + log.error("Neither role, group, or user was configured as part of init-param of IdentityFilter for GWT Gadget application."); + handleError(httpRequest, httpResponse, 500); + return; + } + + // Check roles + if (role != null) + { + for (String identityRole : identity.getRoles()) + { + if (role.equals(identityRole)) + { + chain.doFilter(request, response); + return; + } + } + } + + // Check memberships + if (group != null) + { + if (identity.isMemberOf(group)) + { + chain.doFilter(request, response); + return; + } + } + + // Check user + if (user != null) + { + if (user.equals(identity.getUserId())) + { + chain.doFilter(request, response); + return; + } + } + + log.error("GWT Gadget not authorized for user " + identity.getUserId() + ". Check the filter configuration for IdentityFilter in web.xml."); + handleError(httpRequest, httpResponse, 401); + } + + @Override + public void destroy() + { + } + + private void handleError(HttpServletRequest request, HttpServletResponse response, int code) throws IOException + { + if (request.getServletPath().equals("/exportimport/upload")) + { + // Stupid GWT Upload can't properly handle a response.sendError... + response.setContentType("text/plain"); + Writer writer = response.getWriter(); + writer.write("<response><error>Resource not available</error></response>"); + writer.flush(); + writer.close(); + } + else + { + response.sendError(code); + } + } +} Modified: epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/src/main/webapp/WEB-INF/web.xml =================================================================== --- epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/src/main/webapp/WEB-INF/web.xml 2013-02-25 15:07:23 UTC (rev 9180) +++ epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/gadgets/gwtGadgets/src/main/webapp/WEB-INF/web.xml 2013-02-26 01:51:57 UTC (rev 9181) @@ -45,6 +45,32 @@ <param-value>50</param-value> </context-param> +  + <filter> + <filter-name>IdentityFilter</filter-name> + <filter-class>org.gatein.management.gadget.mop.exportimport.server.IdentityFilter</filter-class> +  + <init-param> + <param-name>role</param-name> + <param-value>administrators</param-value> + </init-param> +  +  +  +  + </filter> + + <filter-mapping> + <filter-name>IdentityFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping> +  <servlet> <servlet-name>gtnService</servlet-name>

11 years, 1 month

1
0
0 / 0

gatein SVN: r9180 - epp/portal/branches/embargo.

by do-not-reply＠jboss.org

Author: ghjboss Date: 2013-02-25 10:07:23 -0500 (Mon, 25 Feb 2013) New Revision: 9180 Added: epp/portal/branches/embargo/EPP_5_2_2_GA_BZ913125_BZ913584/ Log: initial import EPP 5.2.2 for BZ913125 and BZ913584

11 years, 1 month

1
0
0 / 0

gatein SVN: r9179 - epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2013-02-24 23:10:23 -0500 (Sun, 24 Feb 2013) New Revision: 9179 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DataImportStrategy.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml Log: Incorporated eXo Platform feedback to the Ref Guide from Patrice's email. Very minor rework Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DataImportStrategy.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DataImportStrategy.xml 2013-02-25 03:58:43 UTC (rev 9178) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DataImportStrategy.xml 2013-02-25 04:10:23 UTC (rev 9179) @@ -31,6 +31,52 @@ </itemizedlist> <para>Each type of object data has some differences in the import strategy. </para> + <para>The modes for the import strategy include the following: + </para> + <itemizedlist> + <listitem> + <para> + <literal>CONSERVE</literal> + </para> + </listitem> + <listitem> + <para> + <literal>MERGE</literal> + </para> + </listitem> + <listitem> + <para> + <literal>INSERT</literal> + </para> + </listitem> + <listitem> + <para> + <literal>OVERWRITE</literal> + </para> + </listitem> + </itemizedlist> + <para> + Each mode indicates how the portal data is imported. The import mode value is set whenever <literal>NewPortalConfigListener</literal> is initiated. If the mode is not set, the default value will be used. The default value is configurable as a UserPortalConfigService initial parameter. For example, the configuration below means that the default value is <literal>MERGE</literal>. + </para> + <programlisting language="XML"> +<component> + <key>org.exoplatform.portal.config.UserPortalConfigService</key> + <type>org.exoplatform.portal.config.UserPortalConfigService</type> + <component-plugins> + ............ + </component-plugins> + <init-params> + <value-param> + <name>default.import.mode</name> + <value>merge</value> + </value-param> + </init-params> +</component> + +</programlisting> + <para> + The way the import strategy works with the import mode will be clearly demonstrated in next sections for each type of data. + </para> <section id="sect-Reference_Guide-Data_Import_Strategy-Portal_Config"> <title>Portal Configuration</title> <para> @@ -116,7 +162,7 @@ </step> </procedure> <para> - Let's see the example with two navigation nodes in each import mode. In this case, there are 2 navigation definitions: + Let's see the example with two navigation nodes in each import mode. In this case, there are two navigation definitions: </para> <programlisting language="XML" role="XML"><node-navigation> <page-nodes> @@ -134,14 +180,14 @@ </node> </page-nodes> </node-navigation></programlisting> -<figure> - <title id="DataImportStrategy-navigation1">Data Import Strategy Navigation1</title> - <mediaobject> - <imageobject> - <imagedata width="444" align="center" fileref="images/DataImportStrategy/navigation1.png" format="PNG"/> - </imageobject> - </mediaobject> -</figure> + <figure> + <title id="DataImportStrategy-navigation1">Data Import Strategy Navigation1</title> + <mediaobject> + <imageobject> + <imagedata width="444" align="center" fileref="images/DataImportStrategy/navigation1.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> <programlisting language="XML" role="XML"><node-navigation> <page-nodes> <node> @@ -154,14 +200,14 @@ </node> </page-nodes> </node-navigation></programlisting> -<figure> - <title id="DataImportStrategy-navigation2">Data Import Strategy Navigation2</title> -<mediaobject> - <imageobject> - <imagedata width="444" align="center" fileref="images/DataImportStrategy/navigation2.png" format="PNG"/> - </imageobject> - </mediaobject> -</figure> + <figure> + <title id="DataImportStrategy-navigation2">Data Import Strategy Navigation2</title> + <mediaobject> + <imageobject> + <imagedata width="444" align="center" fileref="images/DataImportStrategy/navigation2.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> <para> For example, the <emphasis>navigation1</emphasis> is loaded before <emphasis>navigation2</emphasis>. The Navigation Importer processes on two navigation definitions, depending on the Import Mode defined in portal configuration. </para> @@ -173,17 +219,17 @@ <para> With the <literal>CONSERVE</literal> mode, data are only imported when they do not exist. So, if the navigation has been created by the <emphasis>navigation1</emphasis> definition, the <emphasis>navigation2</emphasis> definition does not affect anything on it. We have the result as following </para> -<figure> -<title id="DataImportStrategy-navigation_1">Data Import Strategy Navigation1</title> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/DataImportStrategy/navigation1.png" format="PNG"/> - </imageobject> - <imageobject role="fo"> - <imagedata width="100mm" align="center" fileref="images/DataImportStrategy/navigation1.png" format="PNG"/> - </imageobject> - </mediaobject> -</figure> + <figure> + <title id="DataImportStrategy-navigation_1">Data Import Strategy Navigation1</title> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/DataImportStrategy/navigation1.png" format="PNG"/> + </imageobject> + <imageobject role="fo"> + <imagedata width="100mm" align="center" fileref="images/DataImportStrategy/navigation1.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> </listitem> </varlistentry> <varlistentry> @@ -192,14 +238,14 @@ <para> If a node does not exist, the importer will add new nodes to the navigation tree. You will see the following result: </para> -<figure> -<title id="DataImportStrategy-navigationInsert">Data Import Strategy Navigation_Insert</title> - <mediaobject> - <imageobject> - <imagedata width="444" align="center" fileref="images/DataImportStrategy/navigation_insert.png" format="PNG"/> - </imageobject> - </mediaobject> -</figure> + <figure> + <title id="DataImportStrategy-navigationInsert">Data Import Strategy Navigation_Insert</title> + <mediaobject> + <imageobject> + <imagedata width="444" align="center" fileref="images/DataImportStrategy/navigation_insert.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> <para> Hereafter, the node 'bar' is added to the navigation tree, because it does not exist in the initiated data. Other nodes are kept in the import process. </para> @@ -211,14 +257,14 @@ <para> The <literal>MERGE</literal> mode indicates that a new node is added to the navigation tree, and updates the node data (such node label and node icon in the example) if it exists. </para> -<figure> -<title id="DataImportStrategy-navigationmerge">Data Import Strategy Navigation_Merge</title> - <mediaobject> - <imageobject> - <imagedata width="444" align="center" fileref="images/DataImportStrategy/navigation_merge.png" format="PNG"/> - </imageobject> - </mediaobject> -</figure> + <figure> + <title id="DataImportStrategy-navigationmerge">Data Import Strategy Navigation_Merge</title> + <mediaobject> + <imageobject> + <imagedata width="444" align="center" fileref="images/DataImportStrategy/navigation_merge.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> </listitem> </varlistentry> <varlistentry> @@ -227,67 +273,17 @@ <para> Everything will be destroyed and replaced with new data if the <literal>OVERWRITE</literal> mode is used. </para> -<figure> -<title id="DataImportStrategy-navigation_2">Data Import Strategy Navigation_2</title> - <mediaobject> - <imageobject> - <imagedata width="444" align="center" fileref="images/DataImportStrategy/navigation2.png" format="PNG"/> - </imageobject> - </mediaobject> -</figure> + <figure> + <title id="DataImportStrategy-navigation_2">Data Import Strategy Navigation_2</title> + <mediaobject> + <imageobject> + <imagedata width="444" align="center" fileref="images/DataImportStrategy/navigation2.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> </listitem> </varlistentry> </variablelist> </section> </section> - <section id="sect-Reference_Guide-Data_Import_Strategy-Import_Mode"> - <title>Import Mode</title> - <para> - In this section, the following modes for the import strategy are introduced: - </para> - <itemizedlist> - <listitem> - <para> - <literal>CONSERVE</literal> - </para> - </listitem> - <listitem> - <para> - <literal>MERGE</literal> - </para> - </listitem> - <listitem> - <para> - <literal>INSERT</literal> - </para> - </listitem> - <listitem> - <para> - <literal>OVERWRITE</literal> - </para> - </listitem> - </itemizedlist> - <para> - Each mode indicates how the portal data is imported. The import mode value is set whenever <literal>NewPortalConfigListener</literal> is initiated. If the mode is not set, the default value will be used in this case. The default value is configurable as a UserPortalConfigService initial param. For example, the bellow configuration means that default value is <literal>MERGE</literal>. - </para> - <programlisting language="XML" role="XML"> -<component> - <key>org.exoplatform.portal.config.UserPortalConfigService</key> - <type>org.exoplatform.portal.config.UserPortalConfigService</type> - <component-plugins> - ............ - </component-plugins> - <init-params> - <value-param> - <name>default.import.mode</name> - <value>merge</value> - </value-param> - </init-params> -</component> - -</programlisting> - <para> - The way that the import strategy works with the import mode will be clearly demonstrated in next sections for each type of data. - </para> - </section> </chapter> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2013-02-25 03:58:43 UTC (rev 9178) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2013-02-25 04:10:23 UTC (rev 9179) @@ -5,7 +5,7 @@ ]> <chapter id="chap-Reference_Guide-Portal_Navigation_Configuration"> <title>Portal Navigation Configuration</title> -<remark>Source: https://docs.jboss.org/author/display/GTNPORTAL35/Portal+Navigation+Confi...</remark> + <remark>Source: https://docs.jboss.org/author/display/GTNPORTAL35/Portal+Navigation+Confi...</remark> <section id="sect-Reference_Guide-Portal_Navigation_Configuration-Overview"> <title>Overview</title> <para> @@ -198,12 +198,8 @@ User navigation is the set of nodes and pages that are owned by a user. They are part of the user's dashboard. </para>  <para> - Two files configure the user navigation (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). They are located in the directory "<filename>portal.war/WEB-INF/conf/portal/users/{userName}</filename>". - </para> + Two files configure the user navigation (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). They are located in the directory<filename>JPP_HOME/gatein.ear/portal.war/WEB-INF/conf/portal/user/{userName}</filename>. </para> <para> - The file <filename>eXoGadgets.war/WEB-INF/gadget.xml</filename> defines the gadgets that will be available on a user dashboard. - </para> - <para> The example below shows a dashboard with all of the default gadgets included, as well as an extra currency converter gadget sourced from <ulink url="http://www.google.com/ig/directory?synd=open" type="http">Google Gadgets</ulink>. </para> <programlisting language="XML" role="XML"><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../extras/PortalDevelopment_DefaultPortalNavigationConfiguration/gadgets.xml" parse="text"/></programlisting> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml 2013-02-25 03:58:43 UTC (rev 9178) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml 2013-02-25 04:10:23 UTC (rev 9179) @@ -116,7 +116,7 @@ </para> <note> <para> - It is important to consider whether the image to be mirrored is symmetrical as this will impact it's final appearance. + It is important to consider whether the image to be mirrored is symmetrical as this will impact its final appearance. </para> </note> <para> Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml =================================================================== --- epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2013-02-25 03:58:43 UTC (rev 9178) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2013-02-25 04:10:23 UTC (rev 9179) @@ -74,11 +74,9 @@ <title>Skin Selection</title> <section id="sect-Reference_Guide-Skin_Selection-Skin_Selection_Through_the_User_Interface"> <title>Skin Selection Through the User Interface</title> - <para> - A skin can be selected to be displayed to the user by multiple means. The easiest way to change the skin is to select it through the user interface. An administrator can change the default skin for the portal, or a logged in user can select which skin they would prefer to be displayed. + <para>The easiest way to change a skin is to select it through the user interface. An administrator can change the default skin for the portal, or a logged in user can select which skin they would prefer to be displayed. </para> - <para> - Please see the <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/" type="http">User Guide</ulink> for information on how to change the skin using the user interface. + <para>For more information about changing skins, see the JBoss Portal Platform User Guide at <ulink url="https://access.redhat.com/knowledge/docs/en-US/JBoss_Portal_Platform/6/ht..." type="http"/>. </para> </section> <section id="sect-Reference_Guide-Skin_Selection-Setting_the_Default_Skin_within_the_Configuration_Files"> @@ -556,7 +554,7 @@ JBoss Portal Platform relies heavily on CSS to create the layout and effects for the UI. Some common techniques for customizing JBoss Portal Platform CSS are explained below. </para> <section id="sect-Reference_Guide-Some_CSS_Techniques-Border_Pattern"> - <title>Border Pattern</title> + <title>Decorator Pattern</title> <para> The decorator is a pattern to create a contour or a curve around an area. In order to achieve this effect you need to create nine cells. The <literal>BODY</literal> is the central area that you want to decorate. The other eight cells are distributed around the <literal>BODY</literal> cell. You can use the width, height and background image properties to achieve any decoration effect that you want. </para>

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-commits February 2013