Execute hooks on backend user login
When a user successfully logs in to the backend of TYPO3, registered hooks should be executed.
This allows TYPO3 core developers as well as extension developers to create functions that react on a BE user login.
Typical use cases for notification services are for example:
- Post a message to Slack or a similar messaging system.
- Send a text message (SMS) to the user's mobile number.
- Pass this event to other systems to monitor suspicious activities.
- Pass this event to other systems for activity logging of specific users (see note below).
- Trigger other events in the system based on the user, user settings, etc.
Note: Some organization/company policies require the governance, compliance, operational auditing, and risk auditing of specific account (e.g. accounts with high privileges such as admins). Developing an extension that notifies a third party system (e.g. via an API call) about the BE login event in real time would be an easy task if a hook would be available.
Currently, backend users can enable the feature "email at login" in their settings. This could be decentralized and moved to a separate extension (or system extension), including some improvements (e.g. generate a nicer HTML email or customize the mail text such as "take the HTTP X-FORWARDED-FOR header into account", etc.). However, I suggest to treat this as a separate task, independent from this feature request.
[FEATURE] Execute hooks on backend user login
When a user successfully logs in to the backend of TYPO3, registered
hooks are executed. This allows for the development of further actions
such as notification services.
Reviewed-by: Markus Klein <email@example.com>
Tested-by: TYPO3com <firstname.lastname@example.org>
Reviewed-by: Michael Schams <email@example.com>
Tested-by: Michael Schams <firstname.lastname@example.org>
Reviewed-by: Joerg Boesche <email@example.com>
Tested-by: Joerg Boesche <firstname.lastname@example.org>
Reviewed-by: Henning Liebe <email@example.com>
Tested-by: Henning Liebe <firstname.lastname@example.org>
Reviewed-by: Reiner Teubner <email@example.com>
Tested-by: Reiner Teubner <firstname.lastname@example.org>
Reviewed-by: Christian Kuhn <email@example.com>
Tested-by: Christian Kuhn <firstname.lastname@example.org>
#6 Updated by Michael Schams about 1 year ago
- Subject changed from Emit signal on successful backend user login to Execute hooks on successful backend user login
- Description updated (diff)
As suggested in review.typo3.org , Hooks should be used, rather than Signals/Slots for consistency reasons.
Therefore this ticket has been updated accordingly (Signal/Slots → Hooks).