Author: smumford
Date: 2011-11-08 23:33:29 -0500 (Tue, 08 Nov 2011)
New Revision: 8014
Modified:
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/configuration/exo-jcr-configuration.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/repository-check-controller.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/PortalDevelopment/Skinning.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml
epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml
Log:
Edits and porting recent updates from ref-guide-eXo-JCR version to standard ref-guide
Modified:
epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml
===================================================================
---
epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-09
03:30:26 UTC (rev 8013)
+++
epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-09
04:33:29 UTC (rev 8014)
@@ -57,10 +57,13 @@
<para>
Users are advised to not run any portal extensions that could override
the data when manipulating the <filename>gatein.ear</filename> file directly.
</para>
+ <para>
+ Remove
<filename>JBOSS_HOME/server/PROFILE/deploy/gatein-sample-extension.ear</filename>
and
<filename>JBOSS_HOME/server/PROFILE/deploy/gatein-sample-portal.ear</filename>
which are packaged by default with &PRODUCT;.
+ </para>
</warning>
</section>
- <section>
+ <section
id="sect-Reference_Guide-SSO_Single_Sign_On-Enabling_SSO_using_JBoss_SSO_Valve">
<title>Enabling SSO using JBoss SSO Valve</title>
<!-- Source Metadata
URL:
https://issues.jboss.org/browse/JBQA-4530
@@ -189,8 +192,8 @@
Once the JBoss SSO Valve has been enabled, it can be tested
with the following steps:
</para>
</formalpara>
- <procedure>
- <title>Testing the SSO Vavle</title>
+ <procedure
id="proc-Reference_Guide-Enabling_SSO_using_JBoss_SSO_Valve-Testing_the_SSO_Valve">
+ <title>Testing the SSO Valve</title>
<step>
<para>
Copy the
<replaceable><PROFILE></replaceable> you enabled the valve in
(<literal>all</literal>, for example) into two new profiles called
<literal>node1</literal> and <literal>node2</literal>.
@@ -398,6 +401,9 @@
To perform the final build step and complete these instructions you will
need the Apache Maven 2. Download it from <ulink type="http"
url="http://maven.apache.org/download.html">here</ulink>.
</para>
</note>
+ <para>
+ Change the default authentication handler with the one provided by JBoss
Enterprise Portal Platform.
+ </para>
<para>
The CAS Server Plugin makes secure callbacks to a RESTful service installed
on the remote JBoss Enterprise Portal Platform server to authenticate a user.
</para>
@@ -418,7 +424,7 @@
<programlisting language="XML" role="XML"><xi:include
href="../../extras/Authentication_Identity_SSO/default102.xml"
parse="text"
xmlns:xi="http://www.w3.org/2001/XInclude"
/></programlisting>
<para>
- with:
+ with the following (ensure you set the host, port and context with the
values corresponding to your portal). Also available in
<filename>GATEIN_SSO_HOME/cas/plugin/WEB-INF/deployerConfigContext.xml</filename>.):
</para>
<programlisting language="XML" role="XML"><xi:include
href="../../extras/Authentication_Identity_SSO/default103.xml"
parse="text"
xmlns:xi="http://www.w3.org/2001/XInclude"
/></programlisting>
@@ -481,16 +487,15 @@
<note>
<remark>Added in gatein commit r7620</remark>
<para>
- By default on logout the CAS server will display the CAS logout page
with a link to return to the portal. To make the CAS server redirect to the portal page
after a logout, modify the
-
<filename>cas.war/WEB-INF/cas-servlet.xml</filename> to include the follow
line :
+ On logout, the CAS server will display the CAS logout page with a link to
return to the portal. To make the CAS server redirect to the portal page after a logout,
modify the <filename>cas.war/WEB-INF/cas-servlet.xml</filename> to include the
follow line :
</para>
<programlisting>
-<bean id="logoutController"
class="org.jasig.cas.web.LogoutController"
-
p:centralAuthenticationService-ref="centralAuthenticationService"
- p:logoutView="casLogoutView"
- p:warnCookieGenerator-ref="warnCookieGenerator"
-
p:ticketGrantingTicketCookieGenerator-ref="ticketGrantingTicketCookieGenerator"
- p:followServiceRedirects="true"/>
+<bean id="logoutController"
class="org.jasig.cas.web.LogoutController"
+ p:centralAuthenticationService-ref="centralAuthenticationService"
+ p:logoutView="casLogoutView"
+ p:warnCookieGenerator-ref="warnCookieGenerator"
+
p:ticketGrantingTicketCookieGenerator-ref="ticketGrantingTicketCookieGenerator"
+ p:followServiceRedirects="true"/>
</programlisting>
</note>
@@ -510,6 +515,14 @@
<para>
There's a line comment already in this source file to assist
you.
</para>
+ <para>
+ In Tomcat, edit
<filename>GATEIN_HOME/conf/jaas.conf</filename>, uncomment on this section and
comment other parts:
+ </para>
+<programlisting>org.gatein.sso.agent.login.SSOLoginModule required;
+org.exoplatform.services.security.j2ee.TomcatLoginModule required
+portalContainerName=portal
+realmName=gatein-domain;
+</programlisting>
</step>
<step>
<para>
@@ -606,6 +619,13 @@
<para>
Extract the package into what will be called
<filename>JOSSO_HOME</filename> in this example.
</para>
+ <warning>
+ <title>JOSSO Versions</title>
+
+ <para>
+ The steps described later are only correct in case of JOSSO
v.1.8.1.
+ </para>
+ </warning>
</step>
</procedure>
@@ -649,7 +669,11 @@
</step>
<step>
<para>
- Tomcat should now start and allow access to <ulink
type="http"
url="http://localhost:8888/josso/signon/login.do">http://localhost:8888/josso/signon/login.do</ulink>
but at this stage login will not be available.
+ Tomcat will start and allow access to
+ <ulink type="http"
url="http://localhost:8888/josso/signon/login.do">
+
http://localhost:8888/josso/signon/login.do
+ </ulink>
+ but at this stage login will not be available.
</para>
<mediaobject>
<imageobject>
@@ -766,12 +790,11 @@
OpenSSO must be purchased from <ulink type="http"
url="http://www.oracle.com/technetwork/middleware/id-mgmt/overview/i...;.
</para>
- </step>
- <!--<step>
+ <step>
<para>
Extract the package into a suitable location. This location will be
referred to as <filename>OPENSSO_HOME</filename> in this example.
</para>
- </step>-->
+ </step>
</procedure>
<para>
@@ -812,7 +835,7 @@
</step>
<step>
<para>
- Copy the following files;
+ Copy the following files into the Tomcat directory at
<filename>TOMCAT_HOME/webapps/opensso/WEB-INF/lib</filename>:
</para>
<itemizedlist>
<listitem>
@@ -831,9 +854,6 @@
</para>
</listitem>
</itemizedlist>
- <para>
- ...into the Tomcat directory at
<filename>TOMCAT_HOME/webapps/opensso/WEB-INF/lib</filename>.
- </para>
</step>
<step>
<para>
@@ -894,7 +914,7 @@
</para>
</step>
<step>
- <procedure>
+ <substeps>
<step>
<para>
Go to the new
"<literal>gatein</literal>" realm and click on the
"<emphasis role="bold">Authentication</emphasis>"
tab.
@@ -910,7 +930,7 @@
Change the selection from
"<literal>Datastore</literal>", which is the default module in
the authentication chain, to
"<literal>AuthenticationPlugin</literal>".
</para>
</step>
- </procedure>
+ </substeps>
<para>
These changes enable authentication of the
"<literal>gatein</literal>" realm using the
<literal>GateIn REST</literal> service instead of the OpenSSO LDAP server.
@@ -925,7 +945,7 @@
<para>
Increase the user privileges to allow REST access with the following
procedure:
</para>
- <procedure>
+ <substeps>
<step>
<para>
Go to "<emphasis role="bold">Access
control</emphasis>", then <emphasis role="bold">Top level
realm</emphasis>, then click on the "<emphasis
role="bold">Privileges</emphasis>" tab and go to
"<emphasis role="bold">All authenticated
users</emphasis>".
@@ -948,7 +968,7 @@
</listitem>
</itemizedlist>
</step>
- </procedure>
+ </substeps>
</step>
<step>
<para>
@@ -957,9 +977,6 @@
</step>
</procedure>
- <!-- <para>
-TODO: The above OpenSSO manual configuration could be replaced by configuration files
prepared in advance
-</para> -->
<procedure
id="proc-Reference_Guide-OpenSSO_The_Open_Web_SSO_project-Setup_the_OpenSSO_client">
<title>Setup the OpenSSO client</title>
<step>
@@ -978,6 +995,16 @@
<programlisting language="XML" role="XML"><xi:include
href="../../extras/Authentication_Identity_SSO/default118.xml"
parse="text"
xmlns:xi="http://www.w3.org/2001/XInclude"
/></programlisting>
</step>
<step>
+ <para>
+ If you are running &PRODUCT; in Tomcat, edit
$GATEIN_HOME/conf/jaas.conf, uncomment on this section and comment other parts:
+ </para>
+<programlisting>org.gatein.sso.agent.login.SSOLoginModule required;
+org.exoplatform.services.security.j2ee.TomcatLoginModule required
+portalContainerName=portal
+realmName=gatein-domain;
+</programlisting>
+ </step>
+ <step>
<para>
Test the installation:
</para>
@@ -1029,17 +1056,16 @@
<para>
Add the following Filters to the top of the filter chain in
<filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>:
</para>
-<remark>DOC NOTE: Please check code sample as updated according to gatein
r7620</remark>
<programlisting language="XML" role="XML"><xi:include
href="../../extras/Authentication_Identity_SSO/default122.xml"
parse="text"
xmlns:xi="http://www.w3.org/2001/XInclude"
/></programlisting>
</step>
- <step>
+<!--<step>
<remark> This step removed in gatein r7647. Should it be removed
here?</remark>
<para>
Replace the <literal>InitiateLoginServlet</literal>
declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>
with:
</para>
<programlisting language="XML" role="XML"><xi:include
href="../../extras/Authentication_Identity_SSO/default123.xml"
parse="text"
xmlns:xi="http://www.w3.org/2001/XInclude"
/></programlisting>
- </step>
+ </step>-->
</procedure>
<para>
@@ -1090,8 +1116,233 @@
<para>
The following procedure outlines how to integrate SPNEGO with the JBoss
Enterprise Portal Platform.
</para>
- <procedure
id="proc-Reference_Guide-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-SPNEGO_Configuration">
- <title>SPNEGO Configuration</title>
+ <note>
+ <title>SPNEGO Basics</title>
+ <para>
+ The procedure below only describes the basic steps to configure the
SPNEGO server. If you are already familiar with SPNEGO, you can jump to the
+ <xref
linkend="proc-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-Advanced_SPNEGO_Configuration"
/>
+ to see how to integrate SPNEGO with JBoss Enterprise Portal Platform.
+ </para>
+ </note>
+ <procedure
id="proc-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-SPNEGO_Basics">
+ <title>SPNEGO Basics</title>
+ <step>
+ <para>
+ Correct the setup of network on the machine. For example, if you are
using the "server.local.network" domain as your machine where Kerberos and
&PRODUCT; are localed, add the line containing the machine's IP address to the
<emphasis role="bold">/etc/host </emphasis> file.
+ </para>
+<programlisting>
+192.168.1.88 server.local.network
+ </programlisting>
+ <note>
+ <para>
+ It is not recommended you use loopback addresses.
+ </para>
+ </note>
+ </step>
+
+ <step>
+ <para>
+ Install Kerberos with these packages: krb5-admin-server, krb5-kdc,
krb5-config, krb5-user, krb5-clients, and krb5-rsh-server.
+ </para>
+ </step>
+
+ <step>
+ <para>
+ Edit the Kerberos configuration file at <emphasis
role="bold">/etc/krb5.config</emphasis>, including:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Uncomment on these lines:
+ </para>
+<programlisting>
+default_tgs_enctypes = des3-hmac-sha1
+default_tkt_enctypes = des3-hmac-sha1
+permitted_enctypes = des3-hmac-sha1
+</programlisting>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add <emphasis
role="bold">local.network</emphasis> as a default realm and it is also
added to the list of realms and remove the remains of realms. The content looks like:
+ </para>
+<programlisting>
+[libdefaults]
+ default_realm = LOCAL.NETWORK
+
+# The following krb5.conf variables are only for MIT Kerberos.
+ krb4_config = /etc/krb.conf
+ krb4_realms = /etc/krb.realms
+ kdc_timesync = 1
+ ccache_type = 4
+ forwardable = true
+ proxiable = true
+
+# The following encryption type specification will be used by MIT Kerberos
+# if uncommented. In general, the defaults in the MIT Kerberos code are
+# correct and overriding these specifications only serves to disable new
+# encryption types as they are added, creating interoperability problems.
+#
+# Thie only time when you might need to uncomment these lines and change
+# the enctypes is if you have local software that will break on ticket
+# caches containing ticket encryption types it doesn't know about (such as
+# old versions of Sun Java).
+
+ default_tgs_enctypes = des3-hmac-sha1
+ default_tkt_enctypes = des3-hmac-sha1
+ permitted_enctypes = des3-hmac-sha1
+
+# The following libdefaults parameters are only for Heimdal Kerberos.
+ v4_instance_resolve = false
+ v4_name_convert = {
+ host = {
+ rcmd = host
+ ftp = ftp
+ }
+ plain = {
+ something = something-else
+ }
+ }
+ fcc-mit-ticketflags = true
+
+[realms]
+ LOCAL.NETWORK = {
+ kdc = server.local.network
+ admin_server = server.local.network
+ }
+
+[domain_realm]
+ .local.network = LOCAL.NETWORK
+ local.network = LOCAL.NETWORK
+
+[login]
+ krb4_convert = true
+ krb4_get_tickets = false
+</programlisting>
+ </listitem>
+ </itemizedlist>
+ </step>
+
+ <step>
+ <para>
+ Edit the KDC configuraton file at <emphasis
role="bold">/etc/krb5kdc/kdc.conf</emphasis> that looks like.
+ </para>
+<programlisting>
+[kdcdefaults]
+ kdc_ports = 750,88
+
+[realms]
+ LOCAL.NETWORK = {
+ database_name = /home/gatein/krb5kdc/principal
+ admin_keytab = FILE:/home/gatein/krb5kdc/kadm5.keytab
+ acl_file = /home/gatein/krb5kdc/kadm5.acl
+ key_stash_file = /home/gatein/krb5kdc/stash
+ kdc_ports = 750,88
+ max_life = 10h 0m 0s
+ max_renewable_life = 7d 0h 0m 0s
+ master_key_type = des3-hmac-sha1
+ supported_enctypes = aes256-cts:normal arcfour-hmac:normal des3-hmac-sha1:normal
des-cbc-crc:normal des:normal des:v4 des:norealm des:onlyrealm des:afs3
+ default_principal_flags = +preauth
+ }
+
+[logging]
+ kdc = FILE:/home/gatein/krb5logs/kdc.log
+ admin_server = FILE:/home/gatein/krb5logs/kadmin.log
+</programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Create krb5kdc and krb5logs directory for Kerberos database as
shown in the configuration file above.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Next, create a KDC database using the following command.
+ </para>
+<programlisting>
+sudo krb5_newrealm
+</programlisting>
+ </listitem>
+
+ <listitem>
+ <para>
+ Start the KDC and Kerberos admin servers using these
commands:
+ </para>
+<programlisting>
+sudo /etc/init.d/krb5-kdc restart
+sudo /etc/init.d/krb-admin-server restart
+</programlisting>
+ </listitem>
+ </itemizedlist>
+ </step>
+
+ <step>
+ <para>
+ Add Principals and create Keys.
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Start an interactive 'kadmin' session and create the
necessary Principals.
+ </para>
+<programlisting>
+sudo kadmin.local
+</programlisting>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add the JBoss Enterprise Portal Platform machine and keytab
file that need to be authenticated.
+ </para>
+<programlisting>
+addprinc -randkey HTTP/server.local.network(a)LOCAL.NETWORK
+ktadd HTTP/server.local.network(a)LOCAL.NETWORK
+</programlisting>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add the default JBoss Enterprise Portal Platform user accounts
and enter the password for each created user that will be authenticated.
+ </para>
+<programlisting>
+addprinc john
+addprinc demo
+addprinc root
+</programlisting>
+ </listitem>
+ </itemizedlist>
+ </step>
+
+ <step>
+ <para>
+ Test your changed setup by using the command.
+ </para>
+<programlisting>
+kinit -A demo
+</programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>
+ If the setup works well, you are required to enter the
password created for this user in Step 5.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ If you want to login with another user, use this command.
+ </para>
+<programlisting>
+kdestroy
+</programlisting>
+ </listitem>
+ </itemizedlist>
+ </step>
+ </procedure>
+ <procedure
id="proc-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-Advanced_SPNEGO_Configuration">
+ <title>Advanced SPNEGO Configuration</title>
<step>
<para>
Activate the Host authentication. Add the following host login module
to the
<filename>jboss-as/server/<replaceable>PROFILE</replaceable>/conf/login-config.xml</filename>:
@@ -1099,7 +1350,8 @@
<programlisting language="XML" role="XML"><xi:include
href="../../extras/Authentication_Identity_SSO/default124.xml"
parse="text"
xmlns:xi="http://www.w3.org/2001/XInclude"
/></programlisting>
<para>
- The '<literal>keyTab</literal>' value should
point to the keytab file that was generated by the <literal>kadmin</literal>
Kerberos tool. See the <ulink type="http"
url="http://community.jboss.org/wiki/SettingupyourKerberosDevelopmen...
up your Kerberos Development Environment</ulink> guide for more details.
+ The '<literal>keyTab</literal>' value should point
to the keytab file that was generated by the <literal>kadmin</literal>
Kerberos tool. See the
+ <xref
linkend="proc-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-SPNEGO_Basics"/>
for more details.
</para>
</step>
<step>
@@ -1178,5 +1430,28 @@
</para>
</section>
+ <section>
+ <title>Clients</title>
+ <para>After performing all configurations above, you need to enable the
<emphasis role="bold">Negotiate authentication </emphasis> of
Firefox in clients so that clients can be authenticated by JBoss Enterprise Portal
Platform as follows:
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Start Firefox, then enter the command: <emphasis
role="bold">about:config </emphasis> into the address field.
+ </para>
+ </step>
+ <step>
+ <para>
+ Enter <emphasis
role="bold">network.negotiate-auth</emphasis> and set the value as
below:
+ </para>
+<programlisting>
+network.negotiate-auth.allow-proxies = true
+network.negotiate-auth.delegation-uris = .local.network
+network.negotiate-auth.gsslib (no-value)
+network.negotiate-auth.trusted-uris = .local.network
+network.negotiate-auth.using-native-gsslib = true
+</programlisting>
+ </step>
+ </procedure>
</section>
Modified:
epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml
===================================================================
---
epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2011-11-09
03:30:26 UTC (rev 8013)
+++
epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2011-11-09
04:33:29 UTC (rev 8014)
@@ -194,7 +194,7 @@
</para>
<variablelist>
<varlistentry>
- <term>gatein-resources.xml</term>
+ <term>WEB-INF/gatein-resources.xml</term>
<listitem>
<para>
For the default portal skin, this file contains definitions for the portal skin,
the window decorations that this skin provides and well as defining some javascript
resources which are not related to the skin. The default portal skin doesn't directly
define portlet skins, these should be provided by the portlets themselves.
@@ -202,7 +202,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>web.xml</term>
+ <term>WEB-INF/web.xml</term>
<listitem>
<para>
For the default portal skin, the <filename>web.xml</filename> of the
<literal>eXoResources.war</literal> will contains a lot of information which
is mostly irrelevant to the portal skinning. The area of interest in this file is the
<literal>resourcerequestfilter</literal> and the fact that the
<parameter>display-name</parameter> is set.
@@ -210,7 +210,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>Stylesheet.CSS</term>
+ <term>skin/Stylesheet.CSS</term>
<listitem>
<para>
This file is the main portal skin stylesheet. It is the main entry point to the CSS
class definitions for the skin. The main content points of this file are:
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml 2011-11-09
03:30:26 UTC (rev 8013)
+++ epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml 2011-11-09
04:33:29 UTC (rev 8014)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.0</edition>
- <pubsnumber>3</pubsnumber>
+ <pubsnumber>4</pubsnumber>
<abstract>
<para>
This Reference Guide is a high-level usage document. It deals with more
advanced topics than the Installation and User Guides, adding new content or taking
concepts discussed in the earlier documents further. It aims to provide supporting
documentation for advanced users of the JBoss Enterprise Portal Platform product. Its
primary focus is on advanced use of the product and it assumes an intermediate or advanced
knowledge of the technology and terms.
Modified: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml
===================================================================
---
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml 2011-11-09
03:30:26 UTC (rev 8013)
+++
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml 2011-11-09
04:33:29 UTC (rev 8014)
@@ -8,6 +8,20 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>5.2.0-4</revnumber>
+ <date>Wed Nov 9 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Republished for review/feedback.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>5.2.0-3</revnumber>
<date>Wed Nov 2 2011</date>
<author>
Modified:
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/configuration/exo-jcr-configuration.xml
===================================================================
---
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/configuration/exo-jcr-configuration.xml 2011-11-09
03:30:26 UTC (rev 8013)
+++
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/configuration/exo-jcr-configuration.xml 2011-11-09
04:33:29 UTC (rev 8014)
@@ -1,4 +1,3 @@
-
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent">
Modified:
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/repository-check-controller.xml
===================================================================
---
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/repository-check-controller.xml 2011-11-09
03:30:26 UTC (rev 8013)
+++
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/eXoJCR/jcr/repository-check-controller.xml 2011-11-09
04:33:29 UTC (rev 8014)
@@ -1,4 +1,3 @@
-
<?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">
Modified:
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml
===================================================================
---
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-09
03:30:26 UTC (rev 8013)
+++
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-09
04:33:29 UTC (rev 8014)
@@ -533,7 +533,7 @@
</note>
<para>
- Change the default authentication handler with the one provided by epp.
+ Change the default authentication handler with the one provided by JBoss
Enterprise Portal Platform.
</para>
<para>
@@ -627,9 +627,7 @@
</procedure>
<!-- Added in gatein commit r7620 -->
<note>
- <remark>
- Added in gatein commit r7620
- </remark>
+ <remark>Added in gatein commit r7620</remark>
<para>
On logout, the CAS server will display the CAS logout page with a link to
return to the portal. To make the CAS server redirect to the portal page after a logout,
modify the <filename>cas.war/WEB-INF/cas-servlet.xml</filename> to include the
follow line :
@@ -734,16 +732,12 @@
Add the following Filters at the top of the filter chain in
<filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>:
</para>
- <remark>
- DOC NOTE: Please check code sample as updated according to gatein
r7620
- </remark>
+<remark>DOC NOTE: Please check code sample as updated according to gatein
r7620</remark>
<programlisting language="XML" role="XML"><xi:include
href="../../extras/Authentication_Identity_SSO/default109.xml"
parse="text"
xmlns:xi="http://www.w3.org/2001/XInclude"
/></programlisting>
</step>
<step>
- <remark>
- This step removed in gatein r7620. Should it be removed here?
- </remark>
+ <remark> This step removed in gatein r7620. Should it be removed
here?</remark>
<para>
Replace the <literal>InitiateLoginServlet</literal>
declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>
with:
@@ -761,11 +755,7 @@
<title>Java Open Single Sign-On Project</title>
<para>
- This Single Sign On plugin enables seamless integration between JBoss
Enterprise Portal Platform and the Java Open Single Sign-On Project (<emphasis
role="bold">JOSSO</emphasis>) Single Sign On Framework. Details about
JOSSO can be found at
- <ulink url="http://www.josso.org">
-
www.josso.org
- </ulink>
- .
+ This Single Sign On plugin enables seamless integration between JBoss
Enterprise Portal Platform and the Java Open Single Sign-On Project (<emphasis
role="bold">JOSSO</emphasis>) Single Sign On Framework. Details about
JOSSO can be found at <ulink
url="http://www.josso.org">www.josso.org</ulink>.
</para>
<para>
@@ -777,11 +767,7 @@
<step>
<para>
- Download JOSSO from
- <ulink type="http"
url="http://sourceforge.net/projects/josso/files/">
-
http://sourceforge.net/projects/josso/files/
- </ulink>
- .
+ Download JOSSO from <ulink type="http"
url="http://sourceforge.net/projects/josso/files/">http://so...;.
</para>
<note>
@@ -899,11 +885,7 @@
<procedure>
<step>
<para>
- Start (or restart) JBoss Enterprise Portal Platform, and
(assuming the JOSSO server on Tomcat is running) direct your browser to
- <ulink type="http"
url="http://localhost:8888/josso/signon/login.do">
-
http://localhost:8888/josso/signon/login.do
- </ulink>
- .
+ Start (or restart) JBoss Enterprise Portal Platform, and
(assuming the JOSSO server on Tomcat is running) direct your browser to <ulink
type="http"
url="http://localhost:8888/josso/signon/login.do">http://localhost:8888/josso/signon/login.do</ulink>.
</para>
</step>
@@ -953,16 +935,12 @@
Add the following Filters to the top of the filter chain in
<filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>:
</para>
- <remark>
- DOC NOTE: Please check code sample as updated according to gatein
r7647
- </remark>
+<remark>DOC NOTE: Please check code sample as updated according to gatein
r7647</remark>
<programlisting language="XML" role="XML"><xi:include
href="../../extras/Authentication_Identity_SSO/default115.xml"
parse="text"
xmlns:xi="http://www.w3.org/2001/XInclude"
/></programlisting>
</step>
<step>
- <remark>
- This step removed in gatein r7647. Should it be removed here?
- </remark>
+ <remark> This step removed in gatein r7647. Should it be removed
here?</remark>
<para>
Replace the <literal>InitiateLoginServlet</literal>
declaration in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>
with:
@@ -994,11 +972,7 @@
<step>
<para>
- OpenSSO must be purchased from
- <ulink type="http"
url="http://www.oracle.com/technetwork/middleware/id-mgmt/overview/i...
- Oracle
- </ulink>
- .
+ OpenSSO must be purchased from <ulink type="http"
url="http://www.oracle.com/technetwork/middleware/id-mgmt/overview/i...;.
</para>
</step>
@@ -1086,11 +1060,7 @@
<step>
<para>
- Tomcat should start and be able to access
- <ulink type="http"
url="http://localhost:8888/opensso/UI/Login?realm=gatein">
-
http://localhost:8888/opensso/UI/Login?realm=gatein
- </ulink>
- .
+ Tomcat should start and be able to access <ulink
type="http"
url="http://localhost:8888/opensso/UI/Login?realm=gatein">http://localhost:8888/opensso/UI/Login?realm=gatein</ulink>.
</para>
<mediaobject>
@@ -1116,10 +1086,7 @@
<step>
<para>
- Direct your browser to
- <ulink type="http"
url="http://localhost:8888/opensso">
-
http://localhost:8888/opensso
- </ulink>
+ Direct your browser to <ulink type="http"
url="http://localhost:8888/opensso">http://localhost:8888/opensso</ulink>
</para>
</step>
@@ -1263,11 +1230,7 @@
<procedure>
<step>
<para>
- Access JBoss Enterprise Portal Platform by going to
- <ulink type="http"
url="http://localhost:8888/opensso/UI/Login?realm=gatein">
-
http://localhost:8888/opensso/UI/Login?realm=gatein
- </ulink>
- (assuming that the OpenSSO server using Tomcat is still
running).
+ Access JBoss Enterprise Portal Platform by going to <ulink
type="http"
url="http://localhost:8888/opensso/UI/Login?realm=gatein">http://localhost:8888/opensso/UI/Login?realm=gatein</ulink>
(assuming that the OpenSSO server using Tomcat is still running).
</para>
</step>
Modified:
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/PortalDevelopment/Skinning.xml
===================================================================
---
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/PortalDevelopment/Skinning.xml 2011-11-09
03:30:26 UTC (rev 8013)
+++
epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/PortalDevelopment/Skinning.xml 2011-11-09
04:33:29 UTC (rev 8014)
@@ -548,7 +548,8 @@
</para>
<programlisting><command>sh jboss-as/bin/run.sh
-Dexo.product.developing=true</command></programlisting>
- <!-- <programlisting language="Java"
role="Java"><xi:include parse="text"
href="../../extras/PortalDevelopment_Skinning/default192.java"
xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> -->
<warning>
+ <!-- <programlisting language="Java"
role="Java"><xi:include parse="text"
href="../../extras/PortalDevelopment_Skinning/default192.java"
xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> -->
+ <warning>
<para>
This option may cause display bugs in some browsers.
</para>