Yes, you are right, I just have found and corrected this issue, it looks run 
perfectly now, but thank you very much!

  "Scott Battaglia" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
  My guess is you didn't tell it that it was an anonymous read and did not 
provide a username/password.  I think you either need to give is a 
username/password or tell it that is an anonymous read.

  -Scott


  On 1/16/07, Jeff <[EMAIL PROTECTED]> wrote:

    Ok, I think I got the log now:

    --------------------
    Jan 16, 2007 10:19:30 PM org.apache.catalina.core.StandardWrapperValve 
invoke
    SEVERE: Servlet.service() for servlet cas threw exception
    javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid 
Credentials] 
            at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3005)
            at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2951)
            at com.sun.jndi.ldap.LdapCtx.processReturnCode (LdapCtx.java:2753)
            ....
    ------------------------
    Hmm.... That's strange, since I've not been provided LDAPS conection. 
However, I generated a certification from LDAP Server and installed it to CAS 
Server by keytool. I got the same exception still! Does any body has idea? 

    Heeeeeeeeeeeeeeelp!!

    Thanks

    Jeff

      "Jeff" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
      Cool! I got a pace! thank you!

      But, actually I got new problem after I put kdapbp-1.0.jar into lib 
directory. It says: "...Invalid property 'authenticatedReadOnly' of bean 
class...", however, after I removed this property from the configuration file, 
I reached the login page successfully. But after I inputed username/password, I 
got the following response: 
      CAS is Unavailable
      A general exception occurred while trying to access CAS. Please notify 
your system administrator. 

      And I can't find any trace ether directly from web page or cas.log file. 
Since my OpenLDAP doesn't support SSL yet, and I saw the common of "This is the 
authentication handler that authenticates services by means of callback via 
SSL, thereby validating a server side SSL certificate." from 
deployerConfigContext.xml, do you think a SSL available LDAP server is 
mandatory? For your clear, I list my questions aboved below:

      1. Why "authenticatedReadOnly" property can't work?
      2. What's means "CAS is Unavailable..."? and how can I get the detail 
information? 
      3. Is the SSL connection to LDAP Server mandatory? What will happend if I 
connect to an Un-SSL available LDAP server?

      Thank you a lot

      Jeff 



        "Scott Battaglia" < [EMAIL PROTECTED]> wrote in message news:[EMAIL 
PROTECTED]
        Spring LDAP 1.1.2 included a new dependency that we were unaware of at 
the time CAS 3.0.6 was created.  You can find the library in the standard 
Spring LDAP  1.1.2 release or download it here:
        
https://svn.sourceforge.net/svnroot/springframework/repos/repo-ext/com/sun/ldapbp/1.0/ldapbp-1.0.jar
 

        -Scott


        On 1/16/07, JA-SIG CAS Community < [EMAIL PROTECTED]> wrote: 
          Hi all

          I installed a Cas server successful, but when I tried to connect CAS 
to
          OpenLDAP, I got the following error message, when I open the login
          interface:

          -------------------------------------------------- 
          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.BindLdapAuthenticationHandler #1060478 ' 
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 .BindLdapAuthenticationHandler#1060478 ' 
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.BindLdapAuthenticationHandler#1060478' 
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.BindLdapAuthenticationHandler#1060478' 
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

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

          As I configured my server forward 
          http://www.ja-sig.org/products/cas/server/ldapauthhandler/index.html 
. I
          didn't find any information for applicationContext.xml configure. who 
can
          tell me what's the problem?

          BTW: My testing environment is CAS 3.0.6. spring-ldap1.1.2 and
          cas-server-ldap-3.0.6 are under WEB-INF/lib directory. 



          _______________________________________________
          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







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

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

Reply via email to