Events not comings to webhook

muravyov.alexey · 24 Dec 2021, 16:55

Hi.
I have installed fusionauth on docker and I have written webhook that do only console.log of post request body.
I use default tenant and have created new application.
I have enabled all webhook events in tenant, enabled webhook in application and enabled self-registration.

When I press 'send' button on webhook test page, I get results by my webhook console.log. So communication works well.

But when I create new account by registration form or try to login I don't see eny events on my webhook. Nothing request coming.

FA version [1.31.0]

Why I get any events? What should I setup else or how to debug this?
Thanks for advice.

muravyov.alexey · 24 Dec 2021, 18:00

I have found that I get nothing in case if in the webhook application settings disabled option 'all applications' and selected my application or all existed applications.

But if I enable option 'all applications' then I start to get events in my webhook. So it looks like a bug.
Is it?

joshua · 4 Jan 2022, 16:20

@muravyov-alexey

I believe this is working as designed. For most use cases, you will want to configure and use webhooks at the tenant level and leave the setting on the application level to "all applications".

More information can be found below.

https://fusionauth.io/docs/v1/tech/events-webhooks/#form-fields-5

Thanks,
Josh

muravyov.alexey · 5 Jan 2022, 09:17

Thanks, @joshua
If I understand correctly when I disable "all applications" option then I will recive only this 3 events :

jwt.public-key.update
jwt.refresh-token.revoke
user.action
and will not recive any other events

Not sure what it is need for, but if it is correct then better put some hint about this in GUI near the option.

Can you give me an example of case to use this option? Thanks.

joshua · 7 Jan 2022, 20:45

@muravyov-alexey

Not sure what it is need for, but if it is correct then better put some hint about this in GUI near the option.

Good suggestion! I have logged an issue for consideration.

https://github.com/FusionAuth/fusionauth-issues/issues/1542

Hmm. In my view, this makes sense. Here are two cases to consider

jwt.refresh-token.revoke - maybe there are some application-level events that need to take place based on this event. In the right context, this might be functionally equivalent to "logging someone out." If someone was logged out (forcibly) from your application, then you might want to take action based on that (remove them from a list, or make another programmatic check, etc).
user.action - maybe this user was actioned for any number of application-specific reasons that you might want to respond to.

Everything else is scoped to a tenant, from my understanding.

I hope this helps. Thanks for the feedback.

Thanks,
Josh