Author: ekopalov Date: 2012-10-15 09:48:28 -0400 (Mon, 15 Oct 2012) New Revision: 8887 Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml Log: partial fix of BZ#850885 Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml 2012-10-12 16:21:28 UTC (rev 8886) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml 2012-10-15 13:48:28 UTC (rev 8887) @@ -214,7 +214,7 @@ <section id="sect-Reference_Guide-Deploying_WSRP-Non_default_Ports_or_Hostnames"> <title>Non-default Ports or Hostnames</title> <para> - JBoss WS (the web service stack that JBoss Enterprise Portal Platform uses) should update the port and host name used in WSDL. Refer to the JBoss WS <ulink url="http://community.jboss.org/wiki/JBossWS-UserGuide#Configuration... guide</ulink> for more information. + JBoss WS (the web service stack that JBoss Enterprise Portal Platform uses) should update the port and host name used in WSDL. Refer to the <citetitle>Web Services</citetitle> chapter in the <citetitle>JBoss Enterprise Application Platform Administration and Configuration Guide</citetitle>. </para> <para> If the host name and port on which the server runs have been modified, the configuration for the Consumer used to consume JBoss Enterprise Portal Platform's "self" Producer will need to be updated. Refer to <xref linkend="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" /> for directions on how to do this. @@ -225,7 +225,7 @@ <section id="sect-Reference_Guide-Deploying_WSRP-Using_WSRP_with_SSL"> <title>Using WSRP with SSL</title> <para> - It is possible to use WSRP over SSL for secure exchange of data. Refer to these <ulink url="http://community.jboss.org/wiki/ConfiguringWSRPforuseoverSSL&qu... for how to do this. + It is possible to use WSRP over SSL for secure exchange of data. Refer to the <citetitle>Web Services</citetitle> chapter in the <citetitle>Administration and Configuration Guide</citetitle>. </para> </section> @@ -286,16 +286,15 @@ JBoss Enterprise Portal Platform uses <application>JBossWS Native</application> to handle ws-security. </para> <para> - Refer to the WS-Security section of the <ulink url="http://www.jboss.org/jbossas/docs/5-x">JBoss AS 5 Administration and Configuration Guide </ulink> for in-depth configuration options. + Refer to the <citetitle>HTTPS Configuration</citetitle> chapter in the <citetitle>Installation Guide</citetitle> and to the <citetitle>Web Services</citetitle> section of the JBoss Enterprise Application Platform 5 Administration and Configuration Guide for in-depth configuration options. </para> <para> - Please note that since the consumer passes its credentials to the producer, the consumer will act at the wss client and the producer will act as the wss server. + Note that since the consumer passes its credentials to the producer, the consumer acts at the wss client and the producer acts as the wss server. </para> <para> The following are the JBossWS Native configuration files which need to be configure for WSRP: </para> <variablelist> - <title></title> <varlistentry> <term>gatein-wsrp-integration.ear/META-INF/gatein-wsse-consumer.xml</term> <listitem> @@ -324,7 +323,7 @@ <section id="sect-Reference_Guide-WSRP_and_WS_Security-WS_Security_Producer_Configuration"> <title>WS-Security Producer Configuration</title> <para> - Other than the JBossWS configuration file mention above, no other configuration changes should be necessary for the producer. + Apart from the changes of the JBossWS configuration file, you do not need to perform any other configuration on the producer. </para> </section> @@ -332,7 +331,7 @@ <section id="sect-Reference_Guide-WSRP_and_WS_Security-WS_Security_Consumer_Configuration"> <title>WS-Security Consumer Configuration</title> <para> - The consumer requires some changes before it will function properly with WS-Security. + The consumer requires some changes before it can function properly with WS-Security. </para> <para> The consumer needs access to the current servlet request since this is used to retrieve the currently authenticated user. In order to access this information, the consumer needs a special servlet-filter added to the portal. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml 2012-10-12 16:21:28 UTC (rev 8886) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml 2012-10-15 13:48:28 UTC (rev 8887) @@ -154,8 +154,8 @@ <section id="wsrp-ports"> <title>Considerations to use WSRP when running JBoss Enterprise Portal Platform on a non-default port or hostname</title> <para> - JBoss WS, the web service stack that JBoss Enterprise Portal Platform uses, is used to update the - port and host name used in WSDL. Refer to <citetitle>JBoss WS user guide</citetitle> for more details. + The web service stack that JBoss Enterprise Portal Platform uses is based on JBoss WS. It updates the + port and host name used in WSDL (for further details refer to the <citetitle>Web Services</citetitle> chapter in the <citetitle>JBoss Enterprise Application Platform Administration and Configuration User Guide</citetitle>). </para> <para> If you have modified the host name and port on which your server runs, make sure that you update the configuration for the consumer used to consume JBoss Enterprise Portal Platform&apos;s &apos;self&apos; producer (refer to <xref linkend="consumer_configuration"/>). @@ -166,10 +166,7 @@ <title>Securing WSRP</title> <section> <title>Considerations to use WSRP with SSL</title> - <para>It is possible to use WSRP over SSL for secure exchange of data. Please refer to the - <ulink url="http://community.jboss.org/wiki/ConfiguringWSRPforuseoverSSL&qu... - on how to do so from - <ulink url="http://community.jboss.org/wiki/GateIn">GateIn&apos;s wiki</ulink>. + <para>It is possible to use WSRP over SSL for secure exchange of data. Configure your server appriopriately as described in the <citetitle>HTTPS Configuration</citetitle> section of the <citetitle>Installation Guide</citetitle>. </para> </section> <section> @@ -201,8 +198,7 @@ to end users, but also requires that the producer and consumer use the same credentials. This means that the username and password must be the same and valid on both servers. </para> - <para>The recommended approach for this situation would be to use a common LDAP configuration. Please - see the user guide on how to configure LDAP for use with JBoss Enterprise Portal Platform + <para>The recommended approach for this situation is to use a common LDAP configuration (refer to chapter <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Integration" />). </para> </important> <para>The GateIn Wiki article, <ulink url="http://community.jboss.org/wiki/GateInWSRPAndWebServiceSecurity... GateIn WSRP and Web Service Security</ulink>, also provides a step-by-step example on how to configure @@ -210,9 +206,8 @@ </para> <section id="wss_configuration"> <title><remark>BZ#839355</remark>WS-Security Configuration</title> - <para>JBoss Enterprise Portal Platform uses JBossWS Native to handle ws-security. Please see the WS-Security section of the - <ulink url="http://www.jboss.org/jbossas/docs/5-x">JBoss AS 5 Administration and Configuration Guide </ulink> for in-depth configuration options. Please note that since the consumer passes its credentials - to the producer, the consumer will act as the wss client and the producer will act as the wss server. + <para>JBoss Enterprise Portal Platform uses JBossWS Native to handle ws-security (refer to the <citetitle>Web Services</citetitle> section of the + <citetitle>JBoss Enterprise Application Platform 5 Administration and Configuration Guide</citetitle>. Note that since the consumer passes its credentials to the producer, the consumer acts as the wss client and the producer acts as the wss server. </para> <para> The following are the JBossWS Native configuration files which need to be configure for WSRP: </para>