Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: onUserLogin Event for Apps Engine #811

Open
XHorizonX opened this issue Dec 5, 2024 · 1 comment
Open

Feature Request: onUserLogin Event for Apps Engine #811

XHorizonX opened this issue Dec 5, 2024 · 1 comment

Comments

@XHorizonX
Copy link

Problem
Currently, there is no way to capture user login events in Rocket.Chat Apps Engine. For systems that require additional actions during user logins—such as checking if a user is deactivated and activating them automatically—this functionality is essential. Specifically, during a login attempt, it is necessary to detect whether the user is deactivated in Rocket.Chat and automatically activate them if needed, allowing them to proceed with their login seamlessly.

Proposed Solution
Add a new event, onUserLogin, to the Apps Engine. This event should trigger whenever a user attempts to log in successfully. The event should provide access to the user's details (e.g., username, ID, and active status). If the user is found to be deactivated in Rocket.Chat, this event would allow the application to automatically activate the user and finalize the login process.

Use Cases
Automatically activating deactivated users during their login attempt, allowing a seamless experience.
Logging user login activities, including both successful and failed login attempts, for auditing purposes.
Triggering custom workflows, notifications, or additional actions upon user login events.

Benefits
This feature would greatly enhance the extensibility of Rocket.Chat by allowing developers to handle user login workflows dynamically. It would make Rocket.Chat more adaptable to environments where systems often require automatic user activation and custom workflows tied to login events.

@samir0607
Copy link

Is this still valid? Can I work on this.....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants