[Flow] Aithentication provider could not be resolved, only in production context

[Carsten Bleicker]

maybe misspelling and osx caseinsensitive filesystem?
LDAPProvider vs. LdapProvider?


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

Carsten Bleicker
Wülfingstraße 1
42477 Radevormwald

E-Mail:	carsten at bleicker.de
Web:	www.bleicker.de
Twitter:	@carstenbleicker
Jabber:	cbleicker at jabber.ccc.de
Telefon:	+49 (0)171-2690845

Am 08.10.2014 um 15:24 schrieb Christian Loock <chl at vkf-renzel.de>:

> Hi everybody,
> 
> I am currently facing some weird issues, when I try to deploy one of our new applications to our production server.
> I use a custom AuthenticationProvider the extends the TYPO3\LdapProvider class, which works great in development context on our dev server, and also when i run the app on the production server in development context. However, when I set the context to production, I get the following exception:
> 
> An authentication provider with the name
>  "RA\ReleaseManager\Security\Authentication\Provider\LDAPProvider" could
>  not be resolved.
> 
> I allready checked the file permissions on the Cache folders, and noticed, that only Flow_ Classes seem to be cached. If i look into Settings.yaml for the production context, I only set the database settings inside there, so this cant be it either. Does anybody have an idea how this behaviour can be explained that it might be caused by using different contexts, when the only difference in settings is the database config?
> 
> I am really lost here, any help would be highly appreciated.
> 
> Cheers,
> 
> Chris
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow