That's what I feared.
Thanks for all.

Gaëtan.


Scott Battaglia a écrit :
The Spring LDAP distribution should include all of the necessary jars for Spring LDAP. "ant war" would not have caught it as all of the items have already been compiled.

Glad to hear it worked for you!
-Scott

On 4/25/07, *Gaetan Dardy* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Damned ! It works.

    Where are the documentation's pages i've missed !!
    I thought the 'ant war' wouldn't have been successful if files
    were missing…
    Is there a way to check dependencies ?

    And yes, this has nothing to do with 444, but at first, i had also
    a problem with my 'deployerConfigContext.xml' ;-)

    Thanks for your help and the fantastic job you (and the team) are
    doing here.
    This mailing list is more efficient and faster than most of the
    (costly) hotlines I know.

    Gaetan.

    Scott Battaglia a écrit :
    Gaetan,

    This has nothing to do with CAS-444.  It means you're missing one
    JAR file :-)  Try including this jar:
    
http://developer.ja-sig.org/maven2/com/sun/jndi/ldap/ldapbp/1.0/ldapbp-1.0.jar
    
<http://developer.ja-sig.org/maven2/com/sun/jndi/ldap/ldapbp/1.0/ldapbp-1.0.jar>

    -Scott

    On 4/25/07, *Gaetan Dardy* <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:

        Hi again,

        I've used the 'deployerConfigContext.xml' in webapp/WEB-INF
        and configured it. The error changes but it still doesn't work.
        So i've drop down the 3.0.7 and tried again the 3.0.5 with
        both 'fast bind' and 'search'. It works well.
        Then,  I started all over from scratch (and used
        'spring-ldap-1.1.2.jar' and 'cas-server-ldap-3.0.7.jar').
        And I still have the message below. I'm feeling such a fool !

        Thnaks for your help.

        Gaetan.

        
------------------------------------------------------------------------------

        The Throwable encountered at context listener initialization
        was:

        org.springframework.beans.factory.BeanCreationException:
        Error creating bean with name 'centralAuthenticationService'
        defined in ServletContext resource
        [/WEB-INF/applicationContext.xml]: Cannot resolve reference
        to bean 'authenticationManager' while setting bean property
        'authenticationManager'; nested exception is
        org.springframework.beans.factory.BeanCreationException:
        Error creating bean with name 'authenticationManager' defined
        in ServletContext resource
        [/WEB-INF/deployerConfigContext.xml]: Cannot create inner
        bean
        'org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler#41dde0'
        of type
        [org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler]
        while setting bean property 'authenticationHandlers' with key
        [1]; nested exception is
        org.springframework.beans.factory.BeanCreationException:
        Error creating bean with name
        'org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler#41dde0'
        defined in ServletContext resource
        [/WEB-INF/deployerConfigContext.xml]: Cannot resolve
        reference to bean 'contextSource' while setting bean property
        'contextSource'; nested exception is
        org.springframework.beans.factory.BeanCreationException:
        Error creating bean with name 'contextSource' defined in
        ServletContext resource [/WEB-INF/deployerConfigContext.xml]:
        Instantiation of bean failed; nested exception is
        java.lang.NoClassDefFoundError:
        com.sun.jndi.ldap.ctl.ResponseControlFactory

        The Throwable encountered at dispatcher servlet
        initialization was:

        org.springframework.beans.factory.BeanCreationException:
        Error creating bean with name 'centralAuthenticationService'
        defined in ServletContext resource
        [/WEB-INF/applicationContext.xml]: Cannot resolve reference
        to bean 'authenticationManager' while setting bean property
        'authenticationManager'; nested exception is
        org.springframework.beans.factory.BeanCreationException:
        Error creating bean with name 'authenticationManager' defined
        in ServletContext resource
        [/WEB-INF/deployerConfigContext.xml]: Cannot create inner
        bean
        'org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler#41dde0'
        of type
        [org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler]
        while setting bean property 'authenticationHandlers' with key
        [1]; nested exception is
        org.springframework.beans.factory.BeanCreationException:
        Error creating bean with name
        'org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler#41dde0'
        defined in ServletContext resource
        [/WEB-INF/deployerConfigContext.xml]: Cannot resolve
        reference to bean 'contextSource' while setting bean property
        'contextSource'; nested exception is
        org.springframework.beans.factory.BeanCreationException:
        Error creating bean with name 'contextSource' defined in
        ServletContext resource [/WEB-INF/deployerConfigContext.xml]:
        Instantiation of bean failed; nested exception is
        java.lang.NoClassDefFoundError:
        com.sun.jndi.ldap.ctl.ResponseControlFactory



        Scott Battaglia a écrit :
        That is just a sample of how to configure ldap handlers.  The config
        file in webapp/WEB-INF is the production config.  Configure your LDAP
        stuff in that.

        -Scott

On 4/18/07, Gaetan Dardy
        <[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> wrote:
        I've used the "deployerConfigContext.xml" located in
        adaptors/ldap/target/classes and customized it :
        I've modified the
        "org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler
        " bean

        and the next one i.e. "contextSource".
        (I've also compared it to the one in the "cas-server-3.0.7/target
        directory/cas-server-ldap-3.0.7.jar".
What puzzled me is that the error is exactly the same as
        3.0.7 RC2 release.

        I read carefully the LDAP part of the Server Deployment 's documentation
        (

        http://www.ja-sig.org/products/cas/server/ldapauthhandler/index.html)
        and  i've tried both fastbind and search-and-bind authentication with
        the same result.

        Does it help ?

        Gaëtan.

        Scott Battaglia a écrit :


        What exactly are you experiencing?  CAS-444 means you are now required
        to inject an instance of HttpClient into the
        HttpBasedServiceCredentaislAuthenticationHandler which the default
        deployerConfigContext.xml

         does for you.

        -Scott

On 4/18/07, *Gaetan Dardy* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
        <mailto:[EMAIL PROTECTED]>>
        wrote:

            Hi,

            I had successfully tested CAS 3.0.5 with a LDAP authentication
            handler.
            Since I switched to the final 3.0.7, I'm still having the


            HttpBasedServiceCredentialsAuthenticationHandler trouble
            ([CAS-444] bug).
            I read all the release notes and documentation I've found, but I'm
            unable to make it work.

            Am I the only one ?


            Is there something I missed ?

            Best regards,

            Gaëtan Dardy.

            _______________________________________________
            Yale CAS mailing list
        [email protected] <mailto:[email protected]> 
<mailto:[email protected]>
            http://tp.its.yale.edu/mailman/listinfo/cas




        --
        -Scott Battaglia

        LinkedIn: http://www.linkedin.com/in/scottbattaglia
        ------------------------------------------------------------------------

        _______________________________________________
        Yale CAS mailing list


        [email protected] <mailto:[email protected]>
        http://tp.its.yale.edu/mailman/listinfo/cas


        _______________________________________________
        Yale CAS mailing list
        [email protected] <mailto:[email protected]>
        http://tp.its.yale.edu/mailman/listinfo/cas




-- -Scott Battaglia

    LinkedIn: http://www.linkedin.com/in/scottbattaglia
    <http://www.linkedin.com/in/scottbattaglia>
    ------------------------------------------------------------------------

    _______________________________________________
    Yale CAS mailing list
    [email protected] <mailto:[email protected]>
    http://tp.its.yale.edu/mailman/listinfo/cas

    _______________________________________________
    Yale CAS mailing list
    [email protected] <mailto:[email protected]>
    http://tp.its.yale.edu/mailman/listinfo/cas




--
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia <http://www.linkedin.com/in/scottbattaglia>
------------------------------------------------------------------------

_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to