You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contrary to what the documentation say it seams that there is no event send to the webhook when a user creates a new email nor when the user updates his account in any other way (as for example by changing his username) on self-hosted hanko server running on docker.
The documentation list the following event types:
Event
Triggers on
user
user creation, user deletion, user update, email creation, email deletion, change of primary email
user.create
user creation
user.delete
user deletion
user.update
user update, email creation, email deletion, change of primary email
user.update.email
email creation, email deletion, change of primary email
user.update.email.create
email creation
user.update.email.delete
email deletion
user.update.email.primary
change of primary email
email.send
an email was send
but independently from how the configuration file is set, the only received events are the following:
Event
user.create
user.delete
user.update.email.delete
user.update.email.primary
email.send
Beside the missing parent events that don't need to be explicitly received if all the subevents are received, this leaves out the fundamental user.update that should be triggered by changes to the user that don't involve user emails (like username changes), and user.update.email.create that's the only way of knowing when a new secondary email is added by the user.
Reproducing the bug
To easily let anybody reproduce the bug I've made a minimal reproduction repository to leave no ambiguity.
The READEME.md file describes how to reproduce the problem but the steps are also listed below:
Setup the repository:
git clone https://github.com/emanuelescarsella/hanko_missing_events_bug_reproduction.git
cd hanko_missing_events_bug_reproduction
npm install
Checklist
Describe the bug
Contrary to what the documentation say it seams that there is no event send to the webhook when a user creates a new email nor when the user updates his account in any other way (as for example by changing his username) on self-hosted hanko server running on docker.
The documentation list the following event types:
but independently from how the configuration file is set, the only received events are the following:
Beside the missing parent events that don't need to be explicitly received if all the subevents are received, this leaves out the fundamental
user.update
that should be triggered by changes to the user that don't involve user emails (like username changes), anduser.update.email.create
that's the only way of knowing when a new secondary email is added by the user.Reproducing the bug
To easily let anybody reproduce the bug I've made a minimal reproduction repository to leave no ambiguity.
The READEME.md file describes how to reproduce the problem but the steps are also listed below:
Open the browser and go to http://localhost:9000 to test several user interactions and visit http://localhost:5000 to validate user emails.
Check the logs of the express server to see what events where received.
Logs
No response
Configuration
Hanko Version
v1.3.1
OS Hanko Backend
None
OS Version Hanko Backend
No response
OS
None
OS Version
No response
Browser Version
No response
Environment
Docker Compose
Additional Context
No response
The text was updated successfully, but these errors were encountered: