Two custom webhook streams got 403 forbidden

Help
,
1

Hi, I have a problem, and could anyone help me with it?
I created a custom webhook with the event ‘User/Behavioral-Successful,’ and it worked fine. Now, I’ve created another webhook with a different PayloadURL and event (‘Login-Successful’). However, I noticed that the health logs are showing a 403 Forbidden error.
Do you have any idea about it? Thanks.

3

Hi @binh.tieu,

Thanks for reaching out to the Auth0 Community!

Could you clarify if these custom webhooks were working previously?

In my experience, the 403 forbidden error indicates that the authorization token is incorrect. You might need to get a new authorization token and supply it in the settings.

I would also encourage you to review our Troubleshoot Custom Webhooks documentation.

Let me know how this goes for you.

Thanks,
Rueben

1 Like
5

Hi,

I recognized that URL is in PAYLOAD URL display different what I initial input.
I inputted “…mazonaws.com/Prod/prod/api/trigger-update-user-verification/EIG_”
but I saw it display “…mazonaws.com/prod/prod/api/trigger-update-user-verification/eig_” after saved.
That’s mean payload URL doesn’t allow uppercase letter.
That’s the reason of error 403 forbidden.
How can I resolve it from Auth0 side.
Thanks,