Re: [uportal-dev] LdapPersonAttributeDao configuration

[Eric Dalquist]

uPortal 3.1 requires Person Directory 1.5






-Eric

SOO KIM wrote:

If you post details (error messages, stack traces from portal.log) we can provide more help. Also this should probably be on [EMAIL PROTECTED] as it isn't related to uPortal framework development

Hi all,




with <person-directory.version>1.1.2<person-directory.version>.

It was unsuccessful.

SOO

I am having the same issue when I try to launch UP3.1 (trunk)-based portal with Active Directory. I am wondering if I can use Person directory 1.1.x instead of 1.5. If I can, how? I tried it with replacing <person-directory.version>1.5.0-SNAPSHOT<person-directory.version> in pom.xml On Fri, Aug 8, 2008 at 9:27 PM, Eric Dalquist <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    One of my many pending emails:
    http://www.ja-sig.org/wiki/display/PDM15/Person+Directory+1.5+Manual

    The person directory configuration is changing for 3.1 due to
    integration of the search functionality. I did take the time to
    write up manual pages with basic examples for all of the main DAOs
    though and they are on the above linked wiki space.

    There will be more documentation once we get to a 3.1 RC about how
    to migrate a config.

    -Eric


    Drew Wills wrote:

        Hey folks (especially Eric),

        It seems that the enhancements to PersonAttributes that appear
        in uP 3.1 bring changes to the way the DAOs are configured in
        spring, and the LdapPersonAttributeDao configuration I have
        for 3.0 doesn't work on trunk/ anymore.

        I've updated much of it, but I'm still not getting the
        memberOf attribute that I'm expecting.  Is there current
        documentation on configuring LdapPersonAttributeDao for 3.1?

        Here's my XML:

           <!-- LDAP Person Attribute Source, uses the default
        ILdapServer via the LdapServices.getDefaultLdapServer method
        call -->
           <bean id="ADAttributeSource"
        
class="org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao">
               <property name="contextSource">
                   <bean
        class="org.springframework.ldap.core.support.LdapContextSource">
                       <property name="url" value="xxx"/>
                       <property name="userDn" value="xxx"/>
                       <property name="password" value="xxx"/>
                       <property name="pooled" value="true"/>
                   </bean>
               </property>
               <property name="queryAttributeMapping">
                   <map>
                       <entry key="username" value="CN" />
                   </map>
               </property>
               <property name="baseDN">
                   <value>xxx</value>
               </property>
               <!--
               <property name="query">
                   <value>(&amp;(objectCategory=user)(CN={0}))</value>
               </property>
                -->
               <property name="resultAttributeMapping">
                   <map>
                       <entry key="memberOf">
                           <value>memberOf</value>
                       </entry>
                   </map>
               </property>
           </bean>

        It feels like my problem is that I don't understand the
        successor to the 'query' property (which is commented out
        above).  I don't know where to put the filter expression -- is
        that part auto-magically handled by the
        'queryAttributeMapping' property somehow?

        drew wills




--
-----------------
SOO IL KIM
kimsooil.com <http://kimsooil.com>
--------------------
--

You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

smime.p7s
Description: S/MIME Cryptographic Signature