portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From a..@apache.org
Subject svn commit: r725977 [42/48] - in /portals/jetspeed-2/portal/trunk: ./ app-servers/security/jboss/src/java/META-INF/jboss-secsvc/ app-servers/security/jboss/src/java/org/apache/jetspeed/appservers/security/jboss/ applications/jetspeed/src/main/javascrip...
Date Fri, 12 Dec 2008 12:07:04 GMT
Modified: portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-rdbms/index.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-rdbms/index.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-rdbms/index.xml (original)
+++ portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-rdbms/index.xml Fri Dec 12 04:06:29 2008
@@ -1,100 +1,100 @@
-<?xml version="1.0" ?>
-<!--
+<?xml version="1.0" ?>
+<!--
     Licensed to the Apache Software Foundation (ASF) under one or more
     contributor license agreements.  See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
-    
-    http://www.apache.org/licenses/LICENSE-2.0
-    
-    Unless required by applicable law or agreed to in writing, software
-    distributed under the License is distributed on an "AS IS" BASIS,
-    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-    See the License for the specific language governing permissions and
-    limitations under the License.
--->
-<document>
-    <properties>
-        <title>Jetspeed-2 RDBMS</title>
-        <authors>
-            <person name="David Le Strat" email="dlestrat@apache.org" />
-        </authors>
-    </properties>
-    <body>
-        <section name="RDBMS Overview">
-            <p>
-            Jetspeed-2 RDBMS component provide a layer of abstraction from the persistence mechanism used by Jetspeed-2.
-            It provides facilities for datasource configuration as well as data access. 
-            </p>
-            <subsection name="Datasource Configuration">
-            <p>
-            Jetspeed-2 uses <a href="http://db.apache.org/ojb/">OJB</a> <code>PersistenceBroker</code> API as its default
-            persistence mechanism.  The <code>ConnectionRepositoryEntry</code> component configures OJB for Jetspeed-2 as well
-            as the properties available under <code>/etc/db-ojb</code> in the Jetspeed-2 source repository or <code>WEB-INF/classes</code>
-            in a deployed instance of Jetspeed-2.
-            </p>
-            <p>
-            The <code>datasource.xml</code> spring assembly configuration file configures <code>ConnectionRepositoryEntry</code> and is located
-            in <code>WEB-INF/assembly/boot</code>.
-            </p>
-            <p>
-            The <code>ConnectionRepositoryEntry</code> configures an entry in OJB's ConnectionRepository according to its properties.
-            The properties <code>driverClassName</code>, <code>url</code>, <code>username</code> and <code>password</code> are used
-			only if no <code>jndiName</code> is set, i.e. if the connection factory uses the driver to create data sources.  The platform
-			settings are derived from the configured  data source or database driver using OJB's <code>JdbcMetadataUtils</code> class.  The default
-			Jetspeed-2 <code>ConnectionRepositoryEntry</code> configuration expose a datasource.
-            <source>
-    &lt;bean id="JetspeedDS" class="org.apache.jetspeed.components.rdbms.ojb.ConnectionRepositoryEntry"&gt;
-      &lt;property name="jndiName"&gt;
-        &lt;value&gt;java:comp/env/jdbc/jetspeed&lt;/value&gt;
-      &lt;/property&gt;
-    &lt;/bean&gt;</source>
-            </p>
-            <p>
-            In order for OJB to be configured properly with Jetspeed-2, the <code>OJB.properties</code> file (located under
-            <code>/etc/db-ojb/OJB.properties</code> in the source tree and <code>WEB-INF/classes</code> in the deployed application)
-            must set:
-            <source>
-    ConnectionManagerClass=org.apache.jetspeed.components.rdbms.ojb.ConnectionManagerImpl</source>
-            instead of:
-            <source>
-    ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryManagedImpl</source>
-            </p>
-            <p>
-            A class diagram of <code>ConnectionRepositoryEntry</code> and <code>ConnectionManagerImpl</code> is
-            provided below:<br/>
-            <img src="../../images/components/connection-repository-c.gif" border="0"/>
-            </p>
-            </subsection>
-            <subsection name="OJB Datasource Configuration">
-            <p>
-            The bean name provided in <code>datasource.xml</code> must match the <code>jdbc-connection-descriptor</code>
-            <code>jcd-alias</code> property (by default <code>JetspeedDS</code>) located in OJB <code>repository_database.xml</code>
-            as illustrated below.
-            <source>
-    &lt;jdbc-connection-descriptor
-        jcd-alias="JetspeedDS"
-        default-connection="true"
-        batch-mode="false"&gt;</source>
-            </p>
-            </subsection>
-            <subsection name="Jetspeed-2 Datasource Configuration in Tomcat">
-            <p>
-            Jetspeed-2 configure the following datasource in Tomcat.  In the source tree, the Tomcat datasource configuration
-            is located under <code>/etc/conf/tomcat</code>.  When deployed Jetspeed-2 in a Tomcat instance, the Jetspeed-2
-            datasource configuration are deployed under <code>${tomcat_home}/conf/Catalina/localhost/jetspeed.xml</code>. If a different
-            portal name is being used for Jetspeed-2, the configuration file will be named accordingly.
-            <source>
-    &lt;Resource name="jdbc/jetspeed" auth="Container"
-                 factory="org.apache.commons.dbcp.BasicDataSourceFactory"
-                 type="javax.sql.DataSource" username="" password=""
-                 driverClassName="org.apache.derby.jdbc.EmbeddedDriver"
-                 url="jdbc:derby:/tmp/productiondb;create=true"
-                 maxActive="100" maxIdle="30" maxWait="10000"/&gt;</source>
-            </p>
-            </subsection>
-        </section>
-    </body>
-</document>
+    the License.  You may obtain a copy of the License at
+    
+    http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<document>
+    <properties>
+        <title>Jetspeed-2 RDBMS</title>
+        <authors>
+            <person name="David Le Strat" email="dlestrat@apache.org" />
+        </authors>
+    </properties>
+    <body>
+        <section name="RDBMS Overview">
+            <p>
+            Jetspeed-2 RDBMS component provide a layer of abstraction from the persistence mechanism used by Jetspeed-2.
+            It provides facilities for datasource configuration as well as data access. 
+            </p>
+            <subsection name="Datasource Configuration">
+            <p>
+            Jetspeed-2 uses <a href="http://db.apache.org/ojb/">OJB</a> <code>PersistenceBroker</code> API as its default
+            persistence mechanism.  The <code>ConnectionRepositoryEntry</code> component configures OJB for Jetspeed-2 as well
+            as the properties available under <code>/etc/db-ojb</code> in the Jetspeed-2 source repository or <code>WEB-INF/classes</code>
+            in a deployed instance of Jetspeed-2.
+            </p>
+            <p>
+            The <code>datasource.xml</code> spring assembly configuration file configures <code>ConnectionRepositoryEntry</code> and is located
+            in <code>WEB-INF/assembly/boot</code>.
+            </p>
+            <p>
+            The <code>ConnectionRepositoryEntry</code> configures an entry in OJB's ConnectionRepository according to its properties.
+            The properties <code>driverClassName</code>, <code>url</code>, <code>username</code> and <code>password</code> are used
+			only if no <code>jndiName</code> is set, i.e. if the connection factory uses the driver to create data sources.  The platform
+			settings are derived from the configured  data source or database driver using OJB's <code>JdbcMetadataUtils</code> class.  The default
+			Jetspeed-2 <code>ConnectionRepositoryEntry</code> configuration expose a datasource.
+            <source>
+    &lt;bean id="JetspeedDS" class="org.apache.jetspeed.components.rdbms.ojb.ConnectionRepositoryEntry"&gt;
+      &lt;property name="jndiName"&gt;
+        &lt;value&gt;java:comp/env/jdbc/jetspeed&lt;/value&gt;
+      &lt;/property&gt;
+    &lt;/bean&gt;</source>
+            </p>
+            <p>
+            In order for OJB to be configured properly with Jetspeed-2, the <code>OJB.properties</code> file (located under
+            <code>/etc/db-ojb/OJB.properties</code> in the source tree and <code>WEB-INF/classes</code> in the deployed application)
+            must set:
+            <source>
+    ConnectionManagerClass=org.apache.jetspeed.components.rdbms.ojb.ConnectionManagerImpl</source>
+            instead of:
+            <source>
+    ConnectionFactoryClass=org.apache.ojb.broker.accesslayer.ConnectionFactoryManagedImpl</source>
+            </p>
+            <p>
+            A class diagram of <code>ConnectionRepositoryEntry</code> and <code>ConnectionManagerImpl</code> is
+            provided below:<br/>
+            <img src="../../images/components/connection-repository-c.gif" border="0"/>
+            </p>
+            </subsection>
+            <subsection name="OJB Datasource Configuration">
+            <p>
+            The bean name provided in <code>datasource.xml</code> must match the <code>jdbc-connection-descriptor</code>
+            <code>jcd-alias</code> property (by default <code>JetspeedDS</code>) located in OJB <code>repository_database.xml</code>
+            as illustrated below.
+            <source>
+    &lt;jdbc-connection-descriptor
+        jcd-alias="JetspeedDS"
+        default-connection="true"
+        batch-mode="false"&gt;</source>
+            </p>
+            </subsection>
+            <subsection name="Jetspeed-2 Datasource Configuration in Tomcat">
+            <p>
+            Jetspeed-2 configure the following datasource in Tomcat.  In the source tree, the Tomcat datasource configuration
+            is located under <code>/etc/conf/tomcat</code>.  When deployed Jetspeed-2 in a Tomcat instance, the Jetspeed-2
+            datasource configuration are deployed under <code>${tomcat_home}/conf/Catalina/localhost/jetspeed.xml</code>. If a different
+            portal name is being used for Jetspeed-2, the configuration file will be named accordingly.
+            <source>
+    &lt;Resource name="jdbc/jetspeed" auth="Container"
+                 factory="org.apache.commons.dbcp.BasicDataSourceFactory"
+                 type="javax.sql.DataSource" username="" password=""
+                 driverClassName="org.apache.derby.jdbc.EmbeddedDriver"
+                 url="jdbc:derby:/tmp/productiondb;create=true"
+                 maxActive="100" maxIdle="30" maxWait="10000"/&gt;</source>
+            </p>
+            </subsection>
+        </section>
+    </body>
+</document>

Propchange: portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-rdbms/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-search/index.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-search/index.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-search/index.xml (original)
+++ portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-search/index.xml Fri Dec 12 04:06:29 2008
@@ -1,83 +1,83 @@
-<?xml version="1.0" ?>
-<!--
+<?xml version="1.0" ?>
+<!--
     Licensed to the Apache Software Foundation (ASF) under one or more
     contributor license agreements.  See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
-    
-    http://www.apache.org/licenses/LICENSE-2.0
-    
-    Unless required by applicable law or agreed to in writing, software
-    distributed under the License is distributed on an "AS IS" BASIS,
-    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-    See the License for the specific language governing permissions and
-    limitations under the License.
--->
-<document>
-    <properties>
-        <title>Jetspeed-2 Search</title>
-        <authors>
-            <person name="David Le Strat" email="dlestrat@apache.org" />
-        </authors>
-    </properties>
-    <body>
-        <section name="Search Overview">
-            <p>
-            Jetspeed-2 provides an integration with the popular <a href="http://lucene.apache.org/">Apache Lucene</a>, 
-            a high-performance, full-featured text search engine library written entirely in Java; a technology suitable
-            for nearly any application that requires full-text search, especially cross-platform.. 
-            </p>
-            <subsection name="SearchEngine Overview">
-            <p>
-            Jetspeed-2 provides a <code>SearchEngine</code> component configured as a spring component.  The <code>SearchEngine</code>
-            component is configured in <code>WEB-INF/assembly/search.xml</code>.  The default implementation based on the embedded Lucene
-            search engine must specify the location of the search index file, the name of the analyzer class (if null the default analyzer
-            <code>StandardAnalyzer</code> is used), whether to optimize after update and the <code>HandlerFactory</code>:
-            <source>
-    &lt;bean id="org.apache.jetspeed.search.SearchEngine"
-  	  class="org.apache.jetspeed.search.lucene.SearchEngineImpl"&gt;
-  	  &lt;constructor-arg index="0"&gt;&lt;value&gt;${applicationRoot}/WEB-INF/search_index&lt;/value&gt;&lt;/constructor-arg&gt;
-  	  &lt;constructor-arg index="1"&gt;&lt;null /&gt;&lt;/constructor-arg&gt;
-  	  &lt;constructor-arg type="boolean"&gt;&lt;valu&gt;true&lt;/value&gt;&lt;/constructor-arg&gt;
-  	  &lt;constructor-arg&gt;&lt;ref bean="org.apache.jetspeed.search.HandlerFactory"/&gt;&lt;/constructor-arg&gt;
-    &lt;/bean&gt;</source>
-    		</p>
-    		<p>
-    		The <code>HandlerFactory</code> provides the <code>SearchEngine</code> with a list of <code>ObjectHandler</code>
-    		that will handle the various document types supported by Jetspeed-2 for search.  By default, Jetspeed-2 supports
-    		portlet instances and portlet definitions as searchable entities.  When portlets are registered to the portal,
-    		<code>searchEngine.add(pa)</code> and <code>searchEngine.add(pa.getPortletDefinitions())</code> are invoked.  This
-    		action updates the Jetspeed-2 search index.  For more information on how portlets are registered to the search engine,
-    		see <code>org.apache.jetspeed.tools.pamanager.PortletApplicationManager</code>.
-            <br/>
-            <img src="../../images/components/searchengine-c.gif" border="0"/>
-            </p>
-            </subsection>
-            <subsection name="Document Handlers Overview">
-            <p>
-            Document Handlers are responsible for the parsing of a specific document type in order to index the relevant document fields.
-            </p>
-            <p>
-            Jetspeed-2 provides 2 document handlers implementations responsible for parsing parsing the documents supported by Jetspeed-2
-            as <code>org.apache.jetspeed.search.ParsedObject</code>.  The <code>ParsedObject</code> specify the list of fields
-            and documents supported by Jetspeed-2 that can then be added to <code>org.apache.lucene.document.Document</code> and
-            written to the index through <code>indexWriter.addDocument(doc)</code> operation of the 
-            <a href="http://lucene.apache.org/java/docs/api/index.html"><code>IndexWriter</code></a>.
-            </p>
-            <p>
-            By default, Jetspeed-2 can index portlet applications and portlet definitions respectively through the
-            <code>PortletApplicationHandler</code> and <code>PortletDefinitionHandler</code>.
-            <br/>
-            <img src="../../images/components/searchhandlers-c.gif" border="0"/>
-            </p>
-            </subsection>
-            <subsection name="An Extensible Framework">
-            <p>
-            As most components in Jetspeed-2, the search engine can easily be extended to support addional document types.
-            </p>
-            </subsection>
-        </section>
-    </body>
+    the License.  You may obtain a copy of the License at
+    
+    http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<document>
+    <properties>
+        <title>Jetspeed-2 Search</title>
+        <authors>
+            <person name="David Le Strat" email="dlestrat@apache.org" />
+        </authors>
+    </properties>
+    <body>
+        <section name="Search Overview">
+            <p>
+            Jetspeed-2 provides an integration with the popular <a href="http://lucene.apache.org/">Apache Lucene</a>, 
+            a high-performance, full-featured text search engine library written entirely in Java; a technology suitable
+            for nearly any application that requires full-text search, especially cross-platform.. 
+            </p>
+            <subsection name="SearchEngine Overview">
+            <p>
+            Jetspeed-2 provides a <code>SearchEngine</code> component configured as a spring component.  The <code>SearchEngine</code>
+            component is configured in <code>WEB-INF/assembly/search.xml</code>.  The default implementation based on the embedded Lucene
+            search engine must specify the location of the search index file, the name of the analyzer class (if null the default analyzer
+            <code>StandardAnalyzer</code> is used), whether to optimize after update and the <code>HandlerFactory</code>:
+            <source>
+    &lt;bean id="org.apache.jetspeed.search.SearchEngine"
+  	  class="org.apache.jetspeed.search.lucene.SearchEngineImpl"&gt;
+  	  &lt;constructor-arg index="0"&gt;&lt;value&gt;${applicationRoot}/WEB-INF/search_index&lt;/value&gt;&lt;/constructor-arg&gt;
+  	  &lt;constructor-arg index="1"&gt;&lt;null /&gt;&lt;/constructor-arg&gt;
+  	  &lt;constructor-arg type="boolean"&gt;&lt;valu&gt;true&lt;/value&gt;&lt;/constructor-arg&gt;
+  	  &lt;constructor-arg&gt;&lt;ref bean="org.apache.jetspeed.search.HandlerFactory"/&gt;&lt;/constructor-arg&gt;
+    &lt;/bean&gt;</source>
+    		</p>
+    		<p>
+    		The <code>HandlerFactory</code> provides the <code>SearchEngine</code> with a list of <code>ObjectHandler</code>
+    		that will handle the various document types supported by Jetspeed-2 for search.  By default, Jetspeed-2 supports
+    		portlet instances and portlet definitions as searchable entities.  When portlets are registered to the portal,
+    		<code>searchEngine.add(pa)</code> and <code>searchEngine.add(pa.getPortletDefinitions())</code> are invoked.  This
+    		action updates the Jetspeed-2 search index.  For more information on how portlets are registered to the search engine,
+    		see <code>org.apache.jetspeed.tools.pamanager.PortletApplicationManager</code>.
+            <br/>
+            <img src="../../images/components/searchengine-c.gif" border="0"/>
+            </p>
+            </subsection>
+            <subsection name="Document Handlers Overview">
+            <p>
+            Document Handlers are responsible for the parsing of a specific document type in order to index the relevant document fields.
+            </p>
+            <p>
+            Jetspeed-2 provides 2 document handlers implementations responsible for parsing parsing the documents supported by Jetspeed-2
+            as <code>org.apache.jetspeed.search.ParsedObject</code>.  The <code>ParsedObject</code> specify the list of fields
+            and documents supported by Jetspeed-2 that can then be added to <code>org.apache.lucene.document.Document</code> and
+            written to the index through <code>indexWriter.addDocument(doc)</code> operation of the 
+            <a href="http://lucene.apache.org/java/docs/api/index.html"><code>IndexWriter</code></a>.
+            </p>
+            <p>
+            By default, Jetspeed-2 can index portlet applications and portlet definitions respectively through the
+            <code>PortletApplicationHandler</code> and <code>PortletDefinitionHandler</code>.
+            <br/>
+            <img src="../../images/components/searchhandlers-c.gif" border="0"/>
+            </p>
+            </subsection>
+            <subsection name="An Extensible Framework">
+            <p>
+            As most components in Jetspeed-2, the search engine can easily be extended to support addional document types.
+            </p>
+            </subsection>
+        </section>
+    </body>
 </document>
\ No newline at end of file

Propchange: portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-search/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-search/using-search.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-search/using-search.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-search/using-search.xml (original)
+++ portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-search/using-search.xml Fri Dec 12 04:06:29 2008
@@ -1,44 +1,44 @@
-<?xml version="1.0" ?>
-<!--
+<?xml version="1.0" ?>
+<!--
     Licensed to the Apache Software Foundation (ASF) under one or more
     contributor license agreements.  See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
-    
-    http://www.apache.org/licenses/LICENSE-2.0
-    
-    Unless required by applicable law or agreed to in writing, software
-    distributed under the License is distributed on an "AS IS" BASIS,
-    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-    See the License for the specific language governing permissions and
-    limitations under the License.
--->
-<document>
-    <properties>
-        <title>Jetspeed-2 Search</title>
-        <authors>
-            <person name="David Le Strat" email="dlestrat@apache.org" />
-        </authors>
-    </properties>
-    <body>
-        <section name="Using Jetspeed Search Engine">
-            <p>
-            Jetspeed-2 <code>SearchEngine</code> exposes a <code>search</code> operation returning <code>SearchResults</code>.
-            The <code>SearchResult</code> can be iterated through to display the result of the search.
-            </p>
-            <subsection name="Portlet Search">
-            <p>
-            Jetspeed-2 <code>SearchEngine</code> is used by the <code>PortletApplicationBrowser</code> portlet to search
-            and retrieve portlet according to a given criteria.
-            <br/>
-            <img src="../../images/components/portlet-search.gif" border="0" />
-            </p>
-            <p>
-            Performing a search for &quot;security&quot; returns all the matching portlets and portlet definitions.
-            </p>
-            </subsection>
-        </section>
-    </body>
+    the License.  You may obtain a copy of the License at
+    
+    http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<document>
+    <properties>
+        <title>Jetspeed-2 Search</title>
+        <authors>
+            <person name="David Le Strat" email="dlestrat@apache.org" />
+        </authors>
+    </properties>
+    <body>
+        <section name="Using Jetspeed Search Engine">
+            <p>
+            Jetspeed-2 <code>SearchEngine</code> exposes a <code>search</code> operation returning <code>SearchResults</code>.
+            The <code>SearchResult</code> can be iterated through to display the result of the search.
+            </p>
+            <subsection name="Portlet Search">
+            <p>
+            Jetspeed-2 <code>SearchEngine</code> is used by the <code>PortletApplicationBrowser</code> portlet to search
+            and retrieve portlet according to a given criteria.
+            <br/>
+            <img src="../../images/components/portlet-search.gif" border="0" />
+            </p>
+            <p>
+            Performing a search for &quot;security&quot; returns all the matching portlets and portlet definitions.
+            </p>
+            </subsection>
+        </section>
+    </body>
 </document>
\ No newline at end of file

Propchange: portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-search/using-search.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-security/config.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-security/config.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-security/config.xml (original)
+++ portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-security/config.xml Fri Dec 12 04:06:29 2008
@@ -1,366 +1,366 @@
-<?xml version="1.0"?>
-<!--
+<?xml version="1.0"?>
+<!--
     Licensed to the Apache Software Foundation (ASF) under one or more
     contributor license agreements.  See the NOTICE file distributed with
     this work for additional information regarding copyright ownership.
     The ASF licenses this file to You under the Apache License, Version 2.0
     (the "License"); you may not use this file except in compliance with
-    the License.  You may obtain a copy of the License at
-    
-    http://www.apache.org/licenses/LICENSE-2.0
-    
-    Unless required by applicable law or agreed to in writing, software
-    distributed under the License is distributed on an "AS IS" BASIS,
-    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-    See the License for the specific language governing permissions and
-    limitations under the License.
--->
-<document>
-    <properties>
-        <title>Jetspeed 2 Security Services Configuration</title>
-        <authors>
-            <person name="David Le Strat" email="dlestrat@apache.org" />
-            <person name="Ate Douma" email="ate@douma.nu" />
-        </authors>
-    </properties>
-    <body>
-        <section name="Default configuration">
-            <p>
-                Jetspeed 2 default security services configuration leverages a relational database as its default persitent datastore for security information.
-                Jetspeed 2 security service provider interface provides a mechanism to replace the default datastore configured.
-            </p>
-            <p>
-                3 files are involved when configuring Jetspeed 2 security SPI. All the SPI configuration files are located under
-                <i>${jetspeed-source-home}/portal/src/webapp/WEB-INF/assembly/</i>
-                .
-            </p>
-            <subsection name="security-atn.xml">
-                <p>
-                    This configuration file provides the login module configuration. Not everyone needs this, as some application may decide to use another
-                    login module other than the one provided.
-                </p>
-            </subsection>
-            <subsection name="security-atz.xml">
-                <p>
-                    This configuration file configures the authorization policy, in J2's case
-                    <a href="atz-jaas.html">RdbmsPolicy</a>
-                    .
-                </p>
-            </subsection>
-            <subsection name="security-managers.xml">
-                <p>This configuration file configures all the managers for security purpose.</p>
-            </subsection>
-            <subsection name="security-providers.xml">
-                <p>This configuration file configures the various providers and weaves the SPI together.</p>
-                <ul>
-                    <li>
-                        <code>AuthenticationProviderProxy</code>
-                        : Configures the list of
-                        <code>AuthenticationProvider</code>
-                        and the default authenticator.
-                        <source>
-                            <![CDATA[
-<bean id="org.apache.jetspeed.security.AuthenticationProviderProxy" 
-   class="org.apache.jetspeed.security.impl.AuthenticationProviderProxyImpl">  	   
-   <constructor-arg >
-      <list>
-         <ref bean="org.apache.jetspeed.security.AuthenticationProvider"/>
-      </list>
-   </constructor-arg>
-  <constructor-arg><value>DefaultAuthenticator</value></constructor-arg>
-</bean>]]>
-                        </source>
-                    </li>
-                    <li>
-                        <code>AuthenticationProvider</code>
-                        : Configures the authentication providers for the current portal implementation. The example below configures the default authenticator
-                        that uses the RDBMS to manage/store user information.
-                        <source>
-                            <![CDATA[
-<bean id="org.apache.jetspeed.security.AuthenticationProvider" 
-  	   class="org.apache.jetspeed.security.impl.AuthenticationProviderImpl">  	   
-   <constructor-arg index="0"><value>DefaultAuthenticator</value></constructor-arg>
-   <constructor-arg index="1"><value>The default authenticator</value></constructor-arg>
-   <constructor-arg index="2"><value>login.conf</value></constructor-arg>
-   <constructor-arg index="3">
-      <ref bean="org.apache.jetspeed.security.spi.CredentialHandler"/>
-   </constructor-arg>
-   <constructor-arg index="4">
-      <ref bean="org.apache.jetspeed.security.spi.UserSecurityHandler"/>
-   </constructor-arg>
-</bean>]]>
-                        </source>
-                    </li>
-                    <li>
-                        <code>AuthorizationProvider</code>
-                        : Configures the policies and instantiates the
-                        <code>SecurityPolicies</code>
-                        that are used for enforcing permissions.  By default, Jetspeed 2 does not load any other 
-                        security policies that may have been configured.  In order to use default policies, set
-                        <code>useDefaultPolicy</code> to <code>true</code>
-                        <source>
-                            <![CDATA[
-<bean id="org.apache.jetspeed.security.AuthorizationProvider" 
-  	  class="org.apache.jetspeed.security.impl.AuthorizationProviderImpl">  	   
-    <constructor-arg index="0">
-        <ref bean="org.apache.jetspeed.security.impl.RdbmsPolicy"/>
-    </constructor-arg>
-    <!-- Does not use the default policy as a default behavior -->
-    <constructor-arg index="1"><value>false</value></constructor-arg>   
-</bean>]]>
-                        </source>
-                    </li>
-                </ul>
-            </subsection>
-            <subsection name="security-spi.xml">
-                <p>This configuration file contains configuration that are common to the authentication and authorization SPIs.</p>
-                <table>
-                    <tr>
-                        <th>Bean</th>
-                        <th>Description</th>
-                    </tr>
-                    <tr>
-                        <td>org.apache.jetspeed.security.spi.SecurityAccess</td>
-                        <td>
-                            Used internally by the default OJB based SPI. Provide access to common action/methods for the various SPI implementations. The
-                            <i>SecurityAccess</i>
-                            bean is used by both the Authentication and Authorization SPIs.
-                        </td>
-                    </tr>
-                </table>
-            </subsection>
-            <subsection name="security-spi-atn.xml">
-                <p>This configuration file contains all the configurations for configuring the authentication SPI.</p>
-                <table>
-                    <tr>
-                        <th>Bean</th>
-                        <th>Description</th>
-                    </tr>
-                    <tr>
-                        <td>org.apache.jetspeed.security.spi.CredentialHandler</td>
-                        <td>
-                            The
-                            <i>CredentialHandler</i>
-                            encapsulates the operations involving manipulation of credentials. The default implementation provides support for password
-                            protection as defined by the
-                            <i>PasswordCredentialProvider</i>
-                            ; as well as lifecycle management of credentials through
-                            <i>InternalPasswordCredentialInterceptor</i>
-                            which can be configured to manages parameters such as maximum number of authentication
-                            failures, maximum life span of a credential in days and how much history to retain for a
-                            given credential.
-                        </td>
-                    </tr>
-                    <tr>
-                        <td>org.apache.jetspeed.security.spi.UserSecurityHandler</td>
-                        <td>
-                            The
-                            <i>UserSecurityHandler</i>
-                            encapuslated all the operations around the user principals.
-                        </td>
-                    </tr>
-                </table>
-                <p>
-                    The following simple <code>CredentialHandler</code> configuration is currently provided
-                    by default with Jetspeed:</p>
-                    <source><![CDATA[
-<!-- require a non-empty password -->
-<bean id="org.apache.jetspeed.security.spi.CredentialPasswordValidator" 
-     class="org.apache.jetspeed.security.spi.impl.DefaultCredentialPasswordValidator"/>
-
-<!-- MessageDigest encode passwords using SHA-1 -->
-<bean id="org.apache.jetspeed.security.spi.CredentialPasswordEncoder" 
-     class="org.apache.jetspeed.security.spi.impl.MessageDigestCredentialPasswordEncoder">
-     <constructor-arg index="0"><value>SHA-1</value></constructor-arg>       
-</bean>       
-
-<!-- allow multiple InternalPasswordCredentialInterceptors to be used for DefaultCredentialHandler --> 
-<bean id="org.apache.jetspeed.security.spi.InternalPasswordCredentialInterceptor"
-     class="org.apache.jetspeed.security.spi.impl.InternalPasswordCredentialInterceptorsProxy">
-     <constructor-arg index="0">
-       <list>
-         <!-- enforce an invalid preset password value in the persisent store is required to be changed -->
-         <bean class="org.apache.jetspeed.security.spi.impl.ValidatePasswordOnLoadInterceptor"/>
-
-         <!-- ensure preset cleartext passwords in the persistent store  will be encoded on first use -->
-         <bean class="org.apache.jetspeed.security.spi.impl.EncodePasswordOnFirstLoadInterceptor"/>
-       </list>
-     </constructor-arg>
-</bean>
-
-<bean id="org.apache.jetspeed.security.spi.PasswordCredentialProvider" 
-     class="org.apache.jetspeed.security.spi.impl.DefaultPasswordCredentialProvider">
-     <constructor-arg index="0">
-       <ref bean="org.apache.jetspeed.security.spi.CredentialPasswordValidator"/>
-     </constructor-arg>       
-     <constructor-arg index="1">
-       <ref bean="org.apache.jetspeed.security.spi.CredentialPasswordEncoder"/>
-     </constructor-arg>       
-</bean>       
-
-<bean id="org.apache.jetspeed.security.spi.CredentialHandler" 
-     class="org.apache.jetspeed.security.spi.impl.DefaultCredentialHandler">       
-     <constructor-arg index="0">
-       <ref bean="org.apache.jetspeed.security.spi.SecurityAccess"/>
-     </constructor-arg>       
-     <constructor-arg index="1">
-       <ref bean="org.apache.jetspeed.security.spi.PasswordCredentialProvider"/>
-     </constructor-arg>       
-     <constructor-arg index="2">
-       <ref bean="org.apache.jetspeed.security.spi.InternalPasswordCredentialInterceptor"/>
-     </constructor-arg>
-</bean>]]>
-                  </source>
-                <p>
-                The above configuration requires not much more than that a password should not be
-                empty and MessageDigest encode it using SHA-1.</p>
-                <p>
-                Before the 2.0-M4 release, Jetspeed came configured with a much stricter configuration, but for
-                first time users of the Portal this was a bit overwelming and also quite difficult to configure
-                differently.</p>
-                <p>
-                With the 2.0-M4 release, the previously provided, and rather complex, 
-                <code>InternalPasswordCredentialInterceptor</code> implementations are split up in single atomic
-                interceptors which can much easier be configured indepedently.</p>
-                <p>
-                An overview of the new interceptors and how related request processing pipeline valves can be
-                configured to provide feedback to the user is provided in the <a href="credentials.html">
-                Credentials Management</a> document.</p>
-                <p>
-                Since the "old" (pre 2.0-M4) interceptors are no longer provided with Jetspeed, the example below
-                shows how to "restore" the old setup using the new interceptors:</p>
-                  <source><![CDATA[
-<!-- require a password of minimum length 6 and at least two numeric characters -->
-<bean id="org.apache.jetspeed.security.spi.CredentialPasswordValidator" 
-     class="org.apache.jetspeed.security.spi.impl.SimpleCredentialPasswordValidator">
-     <constructor-arg index="0"><value>6</value></constructor-arg>       
-     <constructor-arg index="1"><value>2</value></constructor-arg>       
-</bean>
-
-<!-- allow multiple InternalPasswordCredentialInterceptors to be used for DefaultCredentialHandler --> 
-<bean id="org.apache.jetspeed.security.spi.InternalPasswordCredentialInterceptor"
-     class="org.apache.jetspeed.security.spi.impl.InternalPasswordCredentialInterceptorsProxy">
-     <constructor-arg index="0">
-       <list>
-         <!-- enforce an invalid preset password value in the persisent store is required to be changed -->
-         <bean class="org.apache.jetspeed.security.spi.impl.ValidatePasswordOnLoadInterceptor"/>
-
-         <!-- ensure preset cleartext passwords in the persistent store  will be encoded on first use -->
-         <bean class="org.apache.jetspeed.security.spi.impl.EncodePasswordOnFirstLoadInterceptor"/>
-
-         <!-- remember the last 3 passwords used and require a new password to be different from those -->
-         <bean class="org.apache.jetspeed.security.spi.impl.PasswordHistoryInterceptor">
-           <constructor-arg index="0"><value>3</value></constructor-arg>       
-         </bean>
-
-         <!-- Automatically expire a password after 60 days -->
-         <bean class="org.apache.jetspeed.security.spi.impl.PasswordExpirationInterceptor">
-           <constructor-arg index="0"><value>60</value></constructor-arg>       
-         </bean>
-
-         <!-- Automatically disable a password after 3 invalid authentication attempts in a row --> 
-         <bean class="org.apache.jetspeed.security.spi.impl.MaxPasswordAuthenticationFailuresInterceptor">
-           <constructor-arg index="0"><value>3</value></constructor-arg>       
-         </bean>
-       </list>
-     </constructor-arg>
-</bean>]]>
-                  </source>
-                <p>
-                And, make sure something like the following configuration is set for the security related valves in
-                pipelines.xml:</p>
-                  <source><![CDATA[
-<bean id="passwordCredentialValve"
-      class="org.apache.jetspeed.security.impl.PasswordCredentialValveImpl"
-      init-method="initialize">
- <constructor-arg>
-   <!-- expirationWarningDays -->
-   <list>
-     <value>2</value>
-     <value>3</value>
-     <value>7</value>
-   </list>
- </constructor-arg>
-</bean> 
-
-<bean id="loginValidationValve"
-      class="org.apache.jetspeed.security.impl.LoginValidationValveImpl"
-      init-method="initialize">
-  <!-- maxNumberOfAuthenticationFailures
-       This value should be in sync with the value for
-       org.apache.jetspeed.security.spi.impl.MaxPasswordAuthenticationFailuresInterceptor
-       (if used) to make sense.
-       Any value < 2 will suppress the LoginConststants.ERROR_FINAL_LOGIN_ATTEMPT
-       error code when only one last attempt is possible before the credential
-       will be disabled after the next authentication failure.
-  -->
-  <constructor-arg index="0"><value>3</value></constructor-arg>  
-</bean>]]>
-                  </source>
-                <p>
-                Also, make sure the above valves are configured in the <code>jetspeed-pipeline</code> bean.</p>
-                <p>
-                See the <a href="credentials.html#User_interaction">User Interaction</a> section in the
-                Credentials Management document for a description of these valves and their relation to the
-                interceptors configuration.</p>
-            </subsection>
-            <subsection name="security-spi-atz.xml">
-                <p>This configuration file contains all the configurations for configuring the authorization SPI.</p>
-                <table>
-                    <tr>
-                        <th>Bean</th>
-                        <th>Description</th>
-                    </tr>
-                    <tr>
-                        <td>org.apache.jetspeed.security.spi.RoleSecurityHandler</td>
-                        <td>
-                            The
-                            <i>RoleSecurityHandler</i>
-                            encapsulates all the operations around the role principals.
-                        </td>
-                    </tr>
-                    <tr>
-                        <td>org.apache.jetspeed.security.spi.GroupSecurityHandler</td>
-                        <td>
-                            The
-                            <i>GroupSecurityHandler</i>
-                            encapsulates all the operations around the group principals.
-                        </td>
-                    </tr>
-                    <tr>
-                        <td>org.apache.jetspeed.security.spi.SecurityMappingHandler</td>
-                        <td>
-                            The
-                            <i>SecurityMappingHandler</i>
-                            encapsulates all the operations involving mapping between principals. It contains the logic managing hierarchy resolution for
-                            hierarchical principals (roles or groups). The default hierarchy resolution provided is a hierarchy by generalization (see overview
-                            for definitions). A
-                            <i>contructor-arg</i>
-                            can be added to the
-                            <i>SecurityMappingHandler</i>
-                            to change the hierarchy resolution strategy. Jetspeed 2 also support a hierarchy resolution by aggregation.
-                        </td>
-                    </tr>
-                </table>
-                <p>
-                    A sample
-                    <code>SecurityMappingHandler</code>
-                    configuration could be:
-                    <source><![CDATA[
-<!-- Security SPI: SecurityMappingHandler -->
-<bean id="org.apache.jetspeed.security.spi.SecurityMappingHandler" 
-      class="org.apache.jetspeed.security.spi.impl.DefaultSecurityMappingHandler">  	   
-   <constructor-arg >
-      <ref bean="org.apache.jetspeed.security.spi.SecurityAccess"/>
-   </constructor-arg>
-   <!-- Default role hierarchy strategy is by generalization.  
-        Add contructor-arg to change the strategy. -->
-   <!-- Default group hierarchy strategy is by generalization.  
-        Add contructor-arg to change the strategy. -->
-</bean>]]>
-                    </source>
-                </p>
-            </subsection>
-        </section>
-    </body>
-</document>
+    the License.  You may obtain a copy of the License at
+    
+    http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<document>
+    <properties>
+        <title>Jetspeed 2 Security Services Configuration</title>
+        <authors>
+            <person name="David Le Strat" email="dlestrat@apache.org" />
+            <person name="Ate Douma" email="ate@douma.nu" />
+        </authors>
+    </properties>
+    <body>
+        <section name="Default configuration">
+            <p>
+                Jetspeed 2 default security services configuration leverages a relational database as its default persitent datastore for security information.
+                Jetspeed 2 security service provider interface provides a mechanism to replace the default datastore configured.
+            </p>
+            <p>
+                3 files are involved when configuring Jetspeed 2 security SPI. All the SPI configuration files are located under
+                <i>${jetspeed-source-home}/portal/src/webapp/WEB-INF/assembly/</i>
+                .
+            </p>
+            <subsection name="security-atn.xml">
+                <p>
+                    This configuration file provides the login module configuration. Not everyone needs this, as some application may decide to use another
+                    login module other than the one provided.
+                </p>
+            </subsection>
+            <subsection name="security-atz.xml">
+                <p>
+                    This configuration file configures the authorization policy, in J2's case
+                    <a href="atz-jaas.html">RdbmsPolicy</a>
+                    .
+                </p>
+            </subsection>
+            <subsection name="security-managers.xml">
+                <p>This configuration file configures all the managers for security purpose.</p>
+            </subsection>
+            <subsection name="security-providers.xml">
+                <p>This configuration file configures the various providers and weaves the SPI together.</p>
+                <ul>
+                    <li>
+                        <code>AuthenticationProviderProxy</code>
+                        : Configures the list of
+                        <code>AuthenticationProvider</code>
+                        and the default authenticator.
+                        <source>
+                            <![CDATA[
+<bean id="org.apache.jetspeed.security.AuthenticationProviderProxy" 
+   class="org.apache.jetspeed.security.impl.AuthenticationProviderProxyImpl">  	   
+   <constructor-arg >
+      <list>
+         <ref bean="org.apache.jetspeed.security.AuthenticationProvider"/>
+      </list>
+   </constructor-arg>
+  <constructor-arg><value>DefaultAuthenticator</value></constructor-arg>
+</bean>]]>
+                        </source>
+                    </li>
+                    <li>
+                        <code>AuthenticationProvider</code>
+                        : Configures the authentication providers for the current portal implementation. The example below configures the default authenticator
+                        that uses the RDBMS to manage/store user information.
+                        <source>
+                            <![CDATA[
+<bean id="org.apache.jetspeed.security.AuthenticationProvider" 
+  	   class="org.apache.jetspeed.security.impl.AuthenticationProviderImpl">  	   
+   <constructor-arg index="0"><value>DefaultAuthenticator</value></constructor-arg>
+   <constructor-arg index="1"><value>The default authenticator</value></constructor-arg>
+   <constructor-arg index="2"><value>login.conf</value></constructor-arg>
+   <constructor-arg index="3">
+      <ref bean="org.apache.jetspeed.security.spi.CredentialHandler"/>
+   </constructor-arg>
+   <constructor-arg index="4">
+      <ref bean="org.apache.jetspeed.security.spi.UserSecurityHandler"/>
+   </constructor-arg>
+</bean>]]>
+                        </source>
+                    </li>
+                    <li>
+                        <code>AuthorizationProvider</code>
+                        : Configures the policies and instantiates the
+                        <code>SecurityPolicies</code>
+                        that are used for enforcing permissions.  By default, Jetspeed 2 does not load any other 
+                        security policies that may have been configured.  In order to use default policies, set
+                        <code>useDefaultPolicy</code> to <code>true</code>
+                        <source>
+                            <![CDATA[
+<bean id="org.apache.jetspeed.security.AuthorizationProvider" 
+  	  class="org.apache.jetspeed.security.impl.AuthorizationProviderImpl">  	   
+    <constructor-arg index="0">
+        <ref bean="org.apache.jetspeed.security.impl.RdbmsPolicy"/>
+    </constructor-arg>
+    <!-- Does not use the default policy as a default behavior -->
+    <constructor-arg index="1"><value>false</value></constructor-arg>   
+</bean>]]>
+                        </source>
+                    </li>
+                </ul>
+            </subsection>
+            <subsection name="security-spi.xml">
+                <p>This configuration file contains configuration that are common to the authentication and authorization SPIs.</p>
+                <table>
+                    <tr>
+                        <th>Bean</th>
+                        <th>Description</th>
+                    </tr>
+                    <tr>
+                        <td>org.apache.jetspeed.security.spi.SecurityAccess</td>
+                        <td>
+                            Used internally by the default OJB based SPI. Provide access to common action/methods for the various SPI implementations. The
+                            <i>SecurityAccess</i>
+                            bean is used by both the Authentication and Authorization SPIs.
+                        </td>
+                    </tr>
+                </table>
+            </subsection>
+            <subsection name="security-spi-atn.xml">
+                <p>This configuration file contains all the configurations for configuring the authentication SPI.</p>
+                <table>
+                    <tr>
+                        <th>Bean</th>
+                        <th>Description</th>
+                    </tr>
+                    <tr>
+                        <td>org.apache.jetspeed.security.spi.CredentialHandler</td>
+                        <td>
+                            The
+                            <i>CredentialHandler</i>
+                            encapsulates the operations involving manipulation of credentials. The default implementation provides support for password
+                            protection as defined by the
+                            <i>PasswordCredentialProvider</i>
+                            ; as well as lifecycle management of credentials through
+                            <i>InternalPasswordCredentialInterceptor</i>
+                            which can be configured to manages parameters such as maximum number of authentication
+                            failures, maximum life span of a credential in days and how much history to retain for a
+                            given credential.
+                        </td>
+                    </tr>
+                    <tr>
+                        <td>org.apache.jetspeed.security.spi.UserSecurityHandler</td>
+                        <td>
+                            The
+                            <i>UserSecurityHandler</i>
+                            encapuslated all the operations around the user principals.
+                        </td>
+                    </tr>
+                </table>
+                <p>
+                    The following simple <code>CredentialHandler</code> configuration is currently provided
+                    by default with Jetspeed:</p>
+                    <source><![CDATA[
+<!-- require a non-empty password -->
+<bean id="org.apache.jetspeed.security.spi.CredentialPasswordValidator" 
+     class="org.apache.jetspeed.security.spi.impl.DefaultCredentialPasswordValidator"/>
+
+<!-- MessageDigest encode passwords using SHA-1 -->
+<bean id="org.apache.jetspeed.security.spi.CredentialPasswordEncoder" 
+     class="org.apache.jetspeed.security.spi.impl.MessageDigestCredentialPasswordEncoder">
+     <constructor-arg index="0"><value>SHA-1</value></constructor-arg>       
+</bean>       
+
+<!-- allow multiple InternalPasswordCredentialInterceptors to be used for DefaultCredentialHandler --> 
+<bean id="org.apache.jetspeed.security.spi.InternalPasswordCredentialInterceptor"
+     class="org.apache.jetspeed.security.spi.impl.InternalPasswordCredentialInterceptorsProxy">
+     <constructor-arg index="0">
+       <list>
+         <!-- enforce an invalid preset password value in the persisent store is required to be changed -->
+         <bean class="org.apache.jetspeed.security.spi.impl.ValidatePasswordOnLoadInterceptor"/>
+
+         <!-- ensure preset cleartext passwords in the persistent store  will be encoded on first use -->
+         <bean class="org.apache.jetspeed.security.spi.impl.EncodePasswordOnFirstLoadInterceptor"/>
+       </list>
+     </constructor-arg>
+</bean>
+
+<bean id="org.apache.jetspeed.security.spi.PasswordCredentialProvider" 
+     class="org.apache.jetspeed.security.spi.impl.DefaultPasswordCredentialProvider">
+     <constructor-arg index="0">
+       <ref bean="org.apache.jetspeed.security.spi.CredentialPasswordValidator"/>
+     </constructor-arg>       
+     <constructor-arg index="1">
+       <ref bean="org.apache.jetspeed.security.spi.CredentialPasswordEncoder"/>
+     </constructor-arg>       
+</bean>       
+
+<bean id="org.apache.jetspeed.security.spi.CredentialHandler" 
+     class="org.apache.jetspeed.security.spi.impl.DefaultCredentialHandler">       
+     <constructor-arg index="0">
+       <ref bean="org.apache.jetspeed.security.spi.SecurityAccess"/>
+     </constructor-arg>       
+     <constructor-arg index="1">
+       <ref bean="org.apache.jetspeed.security.spi.PasswordCredentialProvider"/>
+     </constructor-arg>       
+     <constructor-arg index="2">
+       <ref bean="org.apache.jetspeed.security.spi.InternalPasswordCredentialInterceptor"/>
+     </constructor-arg>
+</bean>]]>
+                  </source>
+                <p>
+                The above configuration requires not much more than that a password should not be
+                empty and MessageDigest encode it using SHA-1.</p>
+                <p>
+                Before the 2.0-M4 release, Jetspeed came configured with a much stricter configuration, but for
+                first time users of the Portal this was a bit overwelming and also quite difficult to configure
+                differently.</p>
+                <p>
+                With the 2.0-M4 release, the previously provided, and rather complex, 
+                <code>InternalPasswordCredentialInterceptor</code> implementations are split up in single atomic
+                interceptors which can much easier be configured indepedently.</p>
+                <p>
+                An overview of the new interceptors and how related request processing pipeline valves can be
+                configured to provide feedback to the user is provided in the <a href="credentials.html">
+                Credentials Management</a> document.</p>
+                <p>
+                Since the "old" (pre 2.0-M4) interceptors are no longer provided with Jetspeed, the example below
+                shows how to "restore" the old setup using the new interceptors:</p>
+                  <source><![CDATA[
+<!-- require a password of minimum length 6 and at least two numeric characters -->
+<bean id="org.apache.jetspeed.security.spi.CredentialPasswordValidator" 
+     class="org.apache.jetspeed.security.spi.impl.SimpleCredentialPasswordValidator">
+     <constructor-arg index="0"><value>6</value></constructor-arg>       
+     <constructor-arg index="1"><value>2</value></constructor-arg>       
+</bean>
+
+<!-- allow multiple InternalPasswordCredentialInterceptors to be used for DefaultCredentialHandler --> 
+<bean id="org.apache.jetspeed.security.spi.InternalPasswordCredentialInterceptor"
+     class="org.apache.jetspeed.security.spi.impl.InternalPasswordCredentialInterceptorsProxy">
+     <constructor-arg index="0">
+       <list>
+         <!-- enforce an invalid preset password value in the persisent store is required to be changed -->
+         <bean class="org.apache.jetspeed.security.spi.impl.ValidatePasswordOnLoadInterceptor"/>
+
+         <!-- ensure preset cleartext passwords in the persistent store  will be encoded on first use -->
+         <bean class="org.apache.jetspeed.security.spi.impl.EncodePasswordOnFirstLoadInterceptor"/>
+
+         <!-- remember the last 3 passwords used and require a new password to be different from those -->
+         <bean class="org.apache.jetspeed.security.spi.impl.PasswordHistoryInterceptor">
+           <constructor-arg index="0"><value>3</value></constructor-arg>       
+         </bean>
+
+         <!-- Automatically expire a password after 60 days -->
+         <bean class="org.apache.jetspeed.security.spi.impl.PasswordExpirationInterceptor">
+           <constructor-arg index="0"><value>60</value></constructor-arg>       
+         </bean>
+
+         <!-- Automatically disable a password after 3 invalid authentication attempts in a row --> 
+         <bean class="org.apache.jetspeed.security.spi.impl.MaxPasswordAuthenticationFailuresInterceptor">
+           <constructor-arg index="0"><value>3</value></constructor-arg>       
+         </bean>
+       </list>
+     </constructor-arg>
+</bean>]]>
+                  </source>
+                <p>
+                And, make sure something like the following configuration is set for the security related valves in
+                pipelines.xml:</p>
+                  <source><![CDATA[
+<bean id="passwordCredentialValve"
+      class="org.apache.jetspeed.security.impl.PasswordCredentialValveImpl"
+      init-method="initialize">
+ <constructor-arg>
+   <!-- expirationWarningDays -->
+   <list>
+     <value>2</value>
+     <value>3</value>
+     <value>7</value>
+   </list>
+ </constructor-arg>
+</bean> 
+
+<bean id="loginValidationValve"
+      class="org.apache.jetspeed.security.impl.LoginValidationValveImpl"
+      init-method="initialize">
+  <!-- maxNumberOfAuthenticationFailures
+       This value should be in sync with the value for
+       org.apache.jetspeed.security.spi.impl.MaxPasswordAuthenticationFailuresInterceptor
+       (if used) to make sense.
+       Any value < 2 will suppress the LoginConststants.ERROR_FINAL_LOGIN_ATTEMPT
+       error code when only one last attempt is possible before the credential
+       will be disabled after the next authentication failure.
+  -->
+  <constructor-arg index="0"><value>3</value></constructor-arg>  
+</bean>]]>
+                  </source>
+                <p>
+                Also, make sure the above valves are configured in the <code>jetspeed-pipeline</code> bean.</p>
+                <p>
+                See the <a href="credentials.html#User_interaction">User Interaction</a> section in the
+                Credentials Management document for a description of these valves and their relation to the
+                interceptors configuration.</p>
+            </subsection>
+            <subsection name="security-spi-atz.xml">
+                <p>This configuration file contains all the configurations for configuring the authorization SPI.</p>
+                <table>
+                    <tr>
+                        <th>Bean</th>
+                        <th>Description</th>
+                    </tr>
+                    <tr>
+                        <td>org.apache.jetspeed.security.spi.RoleSecurityHandler</td>
+                        <td>
+                            The
+                            <i>RoleSecurityHandler</i>
+                            encapsulates all the operations around the role principals.
+                        </td>
+                    </tr>
+                    <tr>
+                        <td>org.apache.jetspeed.security.spi.GroupSecurityHandler</td>
+                        <td>
+                            The
+                            <i>GroupSecurityHandler</i>
+                            encapsulates all the operations around the group principals.
+                        </td>
+                    </tr>
+                    <tr>
+                        <td>org.apache.jetspeed.security.spi.SecurityMappingHandler</td>
+                        <td>
+                            The
+                            <i>SecurityMappingHandler</i>
+                            encapsulates all the operations involving mapping between principals. It contains the logic managing hierarchy resolution for
+                            hierarchical principals (roles or groups). The default hierarchy resolution provided is a hierarchy by generalization (see overview
+                            for definitions). A
+                            <i>contructor-arg</i>
+                            can be added to the
+                            <i>SecurityMappingHandler</i>
+                            to change the hierarchy resolution strategy. Jetspeed 2 also support a hierarchy resolution by aggregation.
+                        </td>
+                    </tr>
+                </table>
+                <p>
+                    A sample
+                    <code>SecurityMappingHandler</code>
+                    configuration could be:
+                    <source><![CDATA[
+<!-- Security SPI: SecurityMappingHandler -->
+<bean id="org.apache.jetspeed.security.spi.SecurityMappingHandler" 
+      class="org.apache.jetspeed.security.spi.impl.DefaultSecurityMappingHandler">  	   
+   <constructor-arg >
+      <ref bean="org.apache.jetspeed.security.spi.SecurityAccess"/>
+   </constructor-arg>
+   <!-- Default role hierarchy strategy is by generalization.  
+        Add contructor-arg to change the strategy. -->
+   <!-- Default group hierarchy strategy is by generalization.  
+        Add contructor-arg to change the strategy. -->
+</bean>]]>
+                    </source>
+                </p>
+            </subsection>
+        </section>
+    </body>
+</document>

Propchange: portals/jetspeed-2/portal/trunk/src/site/xdoc/components/jetspeed-security/config.xml
------------------------------------------------------------------------------
    svn:eol-style = native



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message