[Flow] Aithentication provider could not be resolved, only in production context
Christian Loock
chl at vkf-renzel.de
Wed Oct 8 15:24:53 CEST 2014
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
More information about the Flow
mailing list