Bug #49046
closed
impossible to use repositories or requests to action controller in auth_service
0%
Description
I've implemented my own auth_service which authenticates my users against an ADLDS (ldap from microsoft).
The service works, but it is really not possible to use repositories or create requests to action controllers.
I tried to inject them via "at inject" which leads to a 'Fatal error: Call to a member function xxxfunction() on a non-object error.' of my repositories.
I tried it with \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('PATH\\TO\\MY\\REPOSITORY'); - same shit again
I tried it with $objectManager = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('TYPO3\\CMS\\Extbase\\Object\\ObjectManager');
$objectManager->get('PATH\\TO\\MY\\REPOSITORY');
which leads to 'Fatal error: Call to a member function versionOL() on a non-object in typo3\sysext\extbase\Classes\Persistence\Generic\Storage\Typo3DbBackend.php on line 1203'
Obviously the problem is that there is no TSFE object... pls fix it or give me some advice how to solve it.
I need the repositories to update and import users while logging in, otherwise I have to use oldschool database operations.
Btw I also tried to use:
$request = $objectManager->get('TYPO3\\CMS\\Extbase\\Mvc\\Request');
$dispatcher = $objectManager->get('TYPO3\\CMS\\Extbase\\Mvc\\Dispatcher');
$response = $objectManager->get('TYPO3\\CMS\\Extbase\\Mvc\\Response');
$request->setArguments(SomeArguments);
$request->setControllerExtensionName('MyExtensionName');
$request->setControllerVendorName('MYVENDORNAME');
$request->setControllerName('MyControllerName');
$request->setControllerActionName('myactionname');
$dispatcher->dispatch($request,$response);
it is just IMPOSSIBLE!
Updated by Wouter Wolters over 11 years ago
- Status changed from New to Needs Feedback
This looks like more an implementation fault then a core issue. Can you ask on the mailinglist for support?
Updated by Philipp Gampe over 11 years ago
You are too early in the bootstrap to use advanced framework magic. Please ask in the newsgroup / forum on how to bootstrap the part you need.
Updated by Alexander Opitz over 11 years ago
BTW: Why not use the existing LDAP Extension, which should work with MS?
Updated by Julian Walter about 11 years ago
Yeah it works with MS, but i needed some special things.
Updated by Alexander Opitz almost 11 years ago
- Is Regression set to No
So could you resolve your problem with help from the mailing list as Wouter and Philipp mentioned?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Updated by Xavier Perseguers over 9 years ago
- Status changed from Closed to Accepted
- Target version set to next-patchlevel
- TYPO3 Version changed from 6.1 to 6.2
I confirm this bug with EXT:ig_ldap_sso_auth v3.0-dev which now uses Extbase repositories during the authentication service.
Problem located in \TYPO3\CMS\Extbase\Persistence\Generic\Storage\Typo3DbBackend::getPageRepository() where $GLOBALS['TSFE']->sys_page is an empty string instead of an object.
My code basically does that:
$objectManager = GeneralUtility::makeInstance('TYPO3\\CMS\\Extbase\\Object\\ObjectManager');
$backendUserGroupRepository = $objectManager->get('TYPO3\\CMS\\Extbase\\Domain\\Repository\\BackendUserGroupRepository');
$userGroup = $userGroupRepository->findByUid(10); // this group exists
This fails with
Table 'typo3_62.tx_extbase_domain_model_backendusergroup' doesn't exist
although yesterday I had the same error (see #66566). This happens when cf_extbase_datamapfactory_datamap has no mapping definition for \TYPO3\CMS\Extbase\Domain\Model\BackendUserGroup (e.g., when cache is cleared and those Core repositories have not yet been used when starting Authentication Service in frontend).
After making sure this is not the case anymore. Bug with ->versionOL() may be reproduced:
Fatal error: Call to a member function versionOL() on string
Problem located in \TYPO3\CMS\Extbase\Persistence\Generic\Storage\Typo3DbBackend::getPageRepository() where $GLOBALS['TSFE']->sys_page is an empty string instead of an object.
Updated by Xavier Perseguers over 9 years ago
So we have basically two bugs here:
Datamap cache¶
The first one is that the datamap cache is not properly instantiated when empty and trying to use a repository during authentication because this happens in initFEuser() (index_ts.php:109) for the initialization of TSFE and this is most probably just too early for the static TS to have been parsed.
Invalid/incomplete TSFE¶
Second is the versionOL() problem due to an invalid/incomplete TSFE.
Updated by Helmut Hummel over 9 years ago
- Status changed from Accepted to Needs Feedback
- TYPO3 Version changed from 6.2 to 7
I don't think that Extbase should manipulate global state even more to make it possible to be run in such an early bootstrap state.
Extbase is not designed to be used in that context. We will have to live with that with at least with TYPO3 6.2
In auth services you should not rely on such high level functionality. You can still abstract your code to retrieve some entities into your own repositorx implementation.
For future versions it might be possible, but only if the Extbase code is going to be more decoupled and does not depend on TYPO3 BE or Frontend context any more.
Such a feature will require a tough refactoring and a conceptual overhaul though.
I'd like to close this as won't fix. Fine with that? We could open an Epic ticket to decouple and modernize Extbase code though, but I'm not sure when we sill prioritize such a task over other things to solve.
Updated by Xavier Perseguers over 9 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
next-patchlevel)
Sure, I fully agree, I just wanted to post a possible solution if someone encounters the same problem again.
To fix the versionOL(), a possible solution is something like that at the beginning of the authentication service:
// Fix for "Fatal error: Call to a member function versionOL() on string"
if (TYPO3_MODE === 'FE' && !is_object($GLOBALS['TSFE']->sys_page)) {
$GLOBALS['TSFE']->sys_page = GeneralUtility::makeInstance('TYPO3\\CMS\\Frontend\\Page\\PageRepository');
}
The missing database mapping for Extbase is much more tough to cleanly handle but a viable solution may be inspired from http://nerdcenter.de/extbase-typo3-authentication-service/