> Compare:
>
> > check_password_callable: [LDAP, checkLDAPPassword]
> > class LDAPclass extends sfGuardSecurityUser {
>
> in the config you say LDAP, but later you call it LDAPclass, this is
> why you get the following error:
Thanks FASI, the error now is solved but it doesn't work with LDAP. I check
frontend_dev.log file and see this:
May 06 17:47:17 symfony [info] {sfPatternRouting} Connect sfRoute
"sf_guard_signin" (/login)
May 06 17:47:17 symfony [info] {sfPatternRouting} Connect sfRoute
"sf_guard_signout" (/logout)
May 06 17:47:17 symfony [info] {sfPatternRouting} Connect sfRoute
"sf_guard_password" (/request_password)
May 06 17:47:17 symfony [info] {sfPatternRouting} Connect sfRoute
"nueva_reservacion" (/modulos/profesores/reservacion/nueva)
May 06 17:47:17 symfony [info] {sfPatternRouting} Connect sfRoute "homepage" (/)
May 06 17:47:17 symfony [info] {sfPatternRouting} Connect sfRoute
"default_index" (/:module)
May 06 17:47:17 symfony [info] {sfPatternRouting} Connect sfRoute "default"
(/:module/:action/*)
May 06 17:47:17 symfony [info] {sfPatternRouting} Connect sfRoute
"sf_guard_signin" (/login)
May 06 17:47:17 symfony [info] {sfPatternRouting} Connect sfRoute
"sf_guard_signout" (/logout)
May 06 17:47:17 symfony [info] {sfPatternRouting} Connect sfRoute
"sf_guard_password" (/request_password)
May 06 17:47:17 symfony [info] {sfPatternRouting} Match route "sf_guard_signin"
(/login) for /login with parameters array ( 'module' => 'sfGuardAuth',
'action' => 'signin',)
May 06 17:47:17 symfony [info] {sfFilterChain} Executing filter
"sfRenderingFilter"
May 06 17:47:17 symfony [info] {sfFilterChain} Executing filter "sfCommonFilter"
May 06 17:47:17 symfony [info] {sfFilterChain} Executing filter
"sfExecutionFilter"
May 06 17:47:17 symfony [info] {sfGuardAuthActions} Call
"sfGuardAuthActions->executeSignin()"
May 06 17:47:17 symfony [debug] {sfPropelLogger} exec: SET NAMES 'utf8'
May 06 17:47:17 symfony [debug] {sfPropelLogger} prepare: SELECT
sf_guard_user.ID, sf_guard_user.USERNAME, sf_guard_user.ALGORITHM,
sf_guard_user.SALT, sf_guard_user.PASSWORD, sf_guard_user.CREATED_AT,
sf_guard_user.LAST_LOGIN, sf_guard_user.IS_ACTIVE, sf_guard_user.IS_SUPER_ADMIN
FROM sf_guard_user WHERE sf_guard_user.USERNAME=:p1 AND
sf_guard_user.IS_ACTIVE=:p2 LIMIT 1
May 06 17:47:17 symfony [debug] {sfPropelLogger} Binding 'rperezm' at position
:p1 w/ PDO type PDO::PARAM_STR
May 06 17:47:17 symfony [debug] {sfPropelLogger} Binding true at position :p2
w/ PDO type PDO::PARAM_BOOL
May 06 17:47:17 symfony [info] {sfPHPView} Render
"D:/Server/www/residencia/plugins/sfGuardPlugin/modules/sfGuardAuth/templates/signinSuccess.php"
May 06 17:47:17 symfony [info] {sfPHPView} Decorate content with
"D:\Server\www\residencia\apps\frontend\templates/layout.php"
May 06 17:47:17 symfony [info] {sfPHPView} Render
"D:\Server\www\residencia\apps\frontend\templates/layout.php"
May 06 17:47:17 symfony [info] {main} Get slot "title"
May 06 17:47:17 symfony [info] {sfWebResponse} Send status "HTTP/1.1 200 OK"
May 06 17:47:17 symfony [info] {sfWebResponse} Send header "Content-Type:
text/html; charset=utf-8"
May 06 17:47:17 symfony [info] {sfWebDebugLogger} Configuration 67.73 ms (9)
May 06 17:47:17 symfony [info] {sfWebDebugLogger} Action "sfGuardAuth/signin"
111.99 ms (1)
May 06 17:47:17 symfony [info] {sfWebDebugLogger} View "Success" for
"sfGuardAuth/signin" 69.17 ms (1)
May 06 17:47:17 symfony [info] {sfWebResponse} Send content (113018 o)
Why it doesn't call the checkLDAPPassword method as I said in the app.yml file?
Cheers
Ing. Reynier Pérez Mira
Dirección Técnica IP
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
