Issue Bug Closed

#103233Custom authentification service does not work anymore in V12

Ralf Hübner 02/29/24, 13:50 updated 03/01/24, 10:13

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!

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 4

  1. Torben Hansen commented and changed status New Needs Feedback 02/29/24, 18:15

    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

  2. Ralf Hübner commented 03/01/24, 07:46

    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.

  3. Ralf Hübner commented 03/01/24, 10:10

    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.

  4. Torben Hansen commented and changed status Needs Feedback Closed 03/01/24, 10:13

    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.