Author: jaredmorgs
Date: 2013-01-30 00:07:43 -0500 (Wed, 30 Jan 2013)
New Revision: 9097
Modified:
epp/docs/branches/6.0/Migration_Notes/en-US/Migration_Notes.xml
epp/docs/branches/6.0/Migration_Notes/en-US/Revision_History.xml
epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml
epp/docs/branches/6.0/Reference_Guide/en-US/modules/WSRP.xml
Log:
Updated Migration Notes and Reference Guide with changes from Marek's email about LDAP
as the Default Store
Modified: epp/docs/branches/6.0/Migration_Notes/en-US/Migration_Notes.xml
===================================================================
(Binary files differ)
Modified: epp/docs/branches/6.0/Migration_Notes/en-US/Revision_History.xml
===================================================================
(Binary files differ)
Modified: epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-01-29 18:00:27
UTC (rev 9096)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/Revision_History.xml 2013-01-30 05:07:43
UTC (rev 9097)
@@ -8,6 +8,21 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>6.0.0-42</revnumber>
+ <date>Tue Jan 27 2013</date>
+ <author>
+ <firstname>Jared</firstname>
+ <surname>Morgan</surname>
+ <email/>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>==Ready for Engineering Field Staff review==</member>
+ <member>Added notes from Marek concerning LDAP as a Default
Store.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>6.0.0-41</revnumber>
<date>Tue Jan 27 2013</date>
<author>
@@ -21,6 +36,7 @@
<member>Incorporated feedback for BZ#903884 "Default Portal
Configuration".</member>
<member>Changed all references to $JBOSS_HOME to JPP_HOME, and added
this file path abbreviation to <xref
linkend="sect-File_Name_Conventions"/>.</member>
<member>Reviewed all file path abbreviations, and remove the
JBOSS_SERVER abbreviation, which was basically the same as JPP_HOME.</member>
+ <member>Added notes from Marek concerning LDAP as a Default
Store.</member>
</simplelist>
</revdescription>
</revision>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2013-01-29
18:00:27 UTC (rev 9096)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2013-01-30
05:07:43 UTC (rev 9097)
@@ -259,9 +259,10 @@
<para>
As you have already learned the services are all singletons, so that
the container creates only one single instance of each container. The services are created
by calling the constructors (called <emphasis>constructor
injection</emphasis>). If there are only zero-arguments constructors
(<code>Foo public Foo(){}</code>) there are no problems to be expected.
That's easy.
</para>
-<!--<para>
- But now look at <ulink
url="https://anonsvn.jboss.org/repos/exo-jcr/core/trunk/exo.core.com...
- </para>--> <para>
+ <para>
+ But now look at <ulink
url="https://anonsvn.jboss.org/repos/exo-jcr/core/trunk/exo.core.com...
+ </para>
+ <para>
This JDBC implementation of BaseOrganizationService interface has
only one constructor:
</para>
<programlisting language="Java" role="Java">public
OrganizationServiceImpl(ListenerService listenerService, DatabaseService
dbService);</programlisting>
Modified:
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml
===================================================================
---
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml 2013-01-29
18:00:27 UTC (rev 9096)
+++
epp/docs/branches/6.0/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml 2013-01-30
05:07:43 UTC (rev 9097)
@@ -273,6 +273,7 @@
</section>
<section
id="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_as_Default_Store">
<title>LDAP as Default Store</title>
+ <remark>Source:
https://docs.jboss.org/author/display/GTNPORTAL35/LDAP+integration#LDAPin...
<para>
Follow the procedure below to set LDAP up as the default identity store
for JBoss Portal Platform. All default accounts and some of groups that come with JBoss
Portal Platform will be created in the LDAP store.
</para>
@@ -331,6 +332,18 @@
</para>
</step>
<step>
+ <para>Uncomment <parameter>
ignoreMappedMembershipTypeGroupList</parameter> under <emphasis>Uncomment for
sample LDAP config</emphasis>.<programlisting
language="XML"><value>
+ <string>/platform/*</string>
+</value>
+<value>
+ <string>/organization/*</string>
+</value></programlisting></para>
+ <important>
+ <para>If this configuration is not uncommented, memberships will be used
as both relationships and roles, which may cause duplicated records in the
GUI.</para>
+ <para>Normally, the same roles being used for LDAP mapping need to be
uncommented. User memberships under the specified groups will be created in Picketlink IDM
only as relationships, and not as roles. </para>
+ </important>
+ </step>
+ <step>
<para>
To use a different LDAP server or directory data, edit the
DS-specific <filename>.xml</filename> file you uncommented in <emphasis
role="bold">Step 4</emphasis> above and change the values to suit your
requirements.
</para>
Modified: epp/docs/branches/6.0/Reference_Guide/en-US/modules/WSRP.xml
===================================================================
--- epp/docs/branches/6.0/Reference_Guide/en-US/modules/WSRP.xml 2013-01-29 18:00:27 UTC
(rev 9096)
+++ epp/docs/branches/6.0/Reference_Guide/en-US/modules/WSRP.xml 2013-01-30 05:07:43 UTC
(rev 9097)
@@ -1081,9 +1081,9 @@
</para>
<para>
Use the usual procedure to log in as a Portal administrator and go to the
Application
- Registry. With the default install, you can just go to
- <ulink
url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclassic%2Fadministration%2Fregistry&username=root&password=gtn">
http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass...
</ulink>
- Add the WSRP Configuration portlet to the Administration category. If you
use the Import Applications
+ Registry. With the default install, you can open the
+ <ulink
url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclassic%2Fadministration%2Fregistry&username=root&password=gtn">Group
> Administration > Application Registry </ulink>
+screen and add the WSRP Configuration portlet to the Administration category. If you use
the Import Applications
functionality, the WSRP Configuration portlet will be automatically added
to the Administration
category.
</para>