Project

General

Profile

Actions

Bug #103233

closed

Custom authentification service does not work anymore in V12

Added by Ralf Hübner 9 months ago. Updated 9 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Authentication
Target version:
-
Start date:
2024-02-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
8.2
Tags:
user authentification
Complexity:
Is Regression:
Sprint Focus:

Description

We have a custom user auth service that worked in V11 but not in V12
The service seems not to be registered. However, where can I see the installed services? The docu shows that this is in "System->Reports->Installed services" but there is only one page with all information but no services.

Thank you!

Actions #1

Updated by Torben Hansen 9 months ago

  • Status changed from New to Needs Feedback

For v12, you can see all installed services in "Configuration -> Registered Services".

There has also been a breaking change for Authentication Services in v12, which now require a valid request token. In scenarios, where you can not provide a valid request token (eg. 3rd party SSO), the PSR-14 event BeforeRequestTokenProcessedEvent is available, so event listeners can set a valid request token.

Docs: https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Events/Events/Core/Authentication/BeforeRequestTokenProcessedEvent.html#beforerequesttokenprocessedevent

Actions #2

Updated by Ralf Hübner 9 months ago

Torben Hansen wrote in #note-1:

For v12, you can see all installed services in "Configuration -> Registered Services".

There has also been a breaking change for Authentication Services in v12, which now require a valid request token. In scenarios, where you can not provide a valid request token (eg. 3rd party SSO), the PSR-14 event BeforeRequestTokenProcessedEvent is available, so event listeners can set a valid request token.

Docs: https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Events/Events/Core/Authentication/BeforeRequestTokenProcessedEvent.html#beforerequesttokenprocessedevent

Hi Torben,
thank you for your support!
If I open the System->Configuration...uff, it ends up in "Allowed memory size ... exhausted". I tried with 16G ;-) PHP Fatal error: Allowed memory size of 17179869184
what the hell needs so much memory?
My custom extensions are very small, the biggest externals are aimeos, sf_register, bootstrap-package.

Actions #3

Updated by Ralf Hübner 9 months ago

Ok, I´ve added the EventListener and the custom auth-service is used. But the problem with the configuration page - allowed memeory size exhausted - exists.

Actions #4

Updated by Torben Hansen 9 months ago

  • Status changed from Needs Feedback to Closed

Sorry, no idead about the memory size problem. This is always system specific. But since your original question is resolved, I will close this issue.

Actions

Also available in: Atom PDF