I'm not an LDAP expert (I'm hoping someone else is).  But its most likely
the search base or the filter.  Different LDAP servers require slightly
different filters.

-Scott

On 5/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Hi Scott,

 Thank you for getting me past the last hurdle (email titled "almost
there").
The cas.log gives me this info when I try to login using LDAP FastBind:

2007-05-09 16:36:34,708 WARN [
org.springframework.ldap.support.LdapContextSource] - Property 'userName'
not set - anonymous context will be used for read-write operations
2007-05-09 16:36:34,714 INFO [
org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler] - No
PasswordEncoder set.  Using default:
org.jasig.cas.authentication.handler.PlainTextPasswordEncoder
2007-05-09 16:36:34,714 INFO [
org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler] - No Class
to Support set.  Using default:
org.jasig.cas.authentication.principal.UsernamePasswordCredentials
2007-05-09 16:36:34,726 INFO [
org.jasig.cas.ticket.proxy.support.Cas20ProxyHandler] - No
UniqueTicketIdGenerator specified for
org.jasig.cas.ticket.proxy.support.Cas20ProxyHandler.  Using
org.jasig.cas.util.DefaultUniqueTicketIdGenerator
2007-05-09 16:36:35,078 INFO [org.jasig.cas.web.ServiceValidateController]
- No authentication specification class set.  Defaulting to
org.jasig.cas.validation.Cas20ProtocolValidationSpecification
2007-05-09 16:36:35,078 INFO [org.jasig.cas.web.ServiceValidateController]
- No successView specified.  Using default of casServiceSuccessView
2007-05-09 16:36:35,078 INFO [org.jasig.cas.web.ServiceValidateController]
- No failureView specified.  Using default of casServiceFailureView
2007-05-09 16:36:35,084 INFO [org.jasig.cas.web.ServiceValidateController]
- No successView specified.  Using default of casServiceSuccessView
2007-05-09 16:36:35,084 INFO [org.jasig.cas.web.ServiceValidateController]
- No failureView specified.  Using default of casServiceFailureView
2007-05-09 16:36:35,111 INFO [
org.jasig.cas.web.flow.AuthenticationViaFormAction] - FormObjectClass not
set.  Using default class of
org.jasig.cas.authentication.principal.UsernamePasswordCredentials with
formObjectName credentials and validator
org.jasig.cas.validation.UsernamePasswordCredentialsValidator.
2007-05-09 16:36:40,873 INFO [
org.jasig.cas.web.flow.AutomaticCookiePathSetterAction] - Setting
ContextPath for cookies to: /cas
2007-05-09 16:36:52,436 INFO [
org.jasig.cas.authentication.AuthenticationManagerImpl] -
AuthenticationHandler:
org.jasig.cas.adaptors.ldap.FastBindLdapAuthenticationHandler failed to
authenticate the user which provided the following credentials: jsalvaggio
2007-05-09 16:36:54,775 INFO [
org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] -
Starting cleaning of expired tickets from ticket registry at [Wed May 09
16:36:54 EDT 2007]
2007-05-09 16:36:54,775 INFO [
org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - 0
found to be removed.  Removing now.
2007-05-09 16:36:54,775 INFO [
org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] -
Finished cleaning of expired tickets from ticket registry at [Wed May 09
16:36:54 EDT 2007]

Can you tell me, please, what I still need to do to configure the LDAP
authentication to work?

Thank you

Joe
_______________________________________________
Yale CAS mailing list
[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]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to