86123[WIP][FEATURE] Introduce `AfterUserAuthenticatedEvent`
Commit message
Review
-
Code review CR 0
-
Verified V 0
Issues 1
Files 2
Review log 45
-
Stefan Bürk uploaded patch set 1 09/16/24, 16:14
-
core-ci voted on patch set 1 V -1 09/16/24, 16:47 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/65910
-
Oli Bartsch commented on patch set 1 09/16/24, 17:14
-
Stefan Bürk commented on patch set 1 09/16/24, 17:34
AbstractUserAuthentication.php:597Reply UnresolvedThe deployable permission set change. Currently only working on be_groups but benni asked if that could not be done for be_users. So either the record ($this->user) must be past and back or the authentication class which allwos user publicly to be set also being internal for now. Other way would be to later add the service to overlay records in some way directly, which benni denied to do within the group resolver alrady and use the event there (which was suitable). Not sure if I have enough power to finish this for the feature freeze and get in. Was a quick shot to have a suitable event in place as the "AfterUserLoggedIn" only fires during the real login process and not on every request. Added the authentication class to be in lign with the AfterUserLoggedIn but did not like that either - added the record then instead. Only pushed to get instance clean to work again other things. So what you thing ? Drop the authclass and add at least the `login_type` as string value to the event along with the record ? -
Stefan Bürk abandoned the change 09/16/24, 18:31
AbstractUserAuthentication.php:597