[portal-commits] JBoss Portal SVN: r6180 - docs/trunk/referenceGuide/en/modules.

Author: bdaw Date: 2007-02-06 19:24:23 -0500 (Tue, 06 Feb 2007) New Revision: 6180 Modified: docs/trunk/referenceGuide/en/modules/identity.xml Log: some docs update on SSL and ExternalContext usage in identity Modified: docs/trunk/referenceGuide/en/modules/identity.xml =================================================================== --- docs/trunk/referenceGuide/en/modules/identity.xml 2007-02-07 00:10:58 UTC (rev 6179) +++ docs/trunk/referenceGuide/en/modules/identity.xml 2007-02-07 00:24:23 UTC (rev 6180) @@ -488,9 +488,72 @@ ]]> </programlisting> + <note> + Under <emphasis role="bold">PORTAL_SOURCES/identity/src/resources/example/</emphasis> you can find a sample ldif that + you can use to populate LDAP server and quickly start playing with it. + </note> </sect1> <sect1> + <title>Configuration of LDAP connection</title> + <sect2> + <title>SSL</title> + <para>The setup is very similar to the one described in LdapLoginModule <ulink url="http://www.jboss.org/wiki/Wiki.jsp?page=LdapLoginModule"&g... page</ulink></para> + <para>You need to modify your identity configuration file and add "protocol"</para> + <programlisting> + <![CDATA[ + <datasource> + <name>LDAP</name> + <config> + ... + <option> + <name>protocol</name> + <value>ssl</value> + </option> + ... + </config> + </datasource> + ]]> + </programlisting> + <para> + Then you need to have LDAP server certificate imported into your keystore. You can use following command: + <programlisting>keytool -import -file ldapcert.der -keystore ldap.truststore</programlisting> + </para> + <para> + Now you need to change the settings to use the alternative truststore. That can be done in the properties-service.xml in deploy directory: + <programlisting> + <![CDATA[ + <attribute name="Properties"> + javax.net.ssl.trustStore=../some/path/to/ldap.truststore + javax.net.ssl.trustStorePassword=somepw + </attribute> + ]]> + </programlisting> + </para> + </sect2> + <sect2> + <title>ExternalContext</title> + <para>Instead of configuring your own connection you can use JNDI context federation mechanism in JBoss Application Server. Configuration of + ExternalContext is described in <ulink url="http://docs.jboss.com/jbossas/guides/j2eeguide/r2/en/html_singl... Application Server documentation</ulink></para> + <para>When you have ExternalContext configured you can use it in JBoss Portal by providing proper JNDI name in the configuration: + <programlisting> + <![CDATA[ + <datasource> + <name>LDAP</name> + <config> + <option> + <name>externalContextJndiName</name> + <value>external/ldap/jboss</value> + </option> + </config> + </datasource> + ]]> + </programlisting> + <note>When using "externalContextJndiName" you don't need to specify any other option for this datasource</note> + </para> + </sect2> + </sect1> + <sect1> <title>Identity configuration</title> <para>At the beginning to understand identity configuration you need to understand how it is designed to work in portal. Different identity services like UserModule, RoleModule and etc are just plain java classes that are instantiated and exposed