Author: rdickens Date: 2013-02-03 23:54:26 -0500 (Sun, 03 Feb 2013) New Revision: 9112 Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml Log: Source: https://docs.jboss.org/author/display/GTNPORTAL35/Clustered+SSO+setup, updated to page version 9 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-04 04:36:06 UTC (rev 9111) +++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2013-02-04 04:54:26 UTC (rev 9112) @@ -1866,6 +1866,7 @@ </section> <section> <title>Clustered Single-Sign On in a Shared DNS Domain</title> + <remark>Sourced from: https://docs.jboss.org/author/display/GTNPORTAL35/Clustered+SSO+setup. Updated to page version: 9</remark> <para> If multiple JBoss Portal Platform servers are accessed through different URLs in the same DNS domain, single sign-on can be configured by adding the <parameter>domain</parameter> parameter to the <parameter>sso</parameter> configuration entry. </para> @@ -1896,6 +1897,8 @@ <programlisting language="XML"><![CDATA[ <sso cache-container="web" cache-name="sso" reauthenticate="false" domain="yourdomain.com"/> ]]></programlisting> + <remark>Source: https://docs.jboss.org/author/display/GTNPORTAL35/Clustered+SSO+setup. Updated to version 9.</remark> + <note><para>By default, <filename>standalone-ha.xml</filename> is configured to use a shared H2 database, which is intended to be used only for testing purposes.</para></note> </step> <step> <para>