You have a couple of options:
you can update webhook so it always returns 200, regardless of the message it receives. This won't work if the webhook URL is incorrect. For example, if you set up the webhook to live at https://exmple.com when it really lives at https://example.com and you don't have access to https://exmple.com. if you have an API key, you can update the webhook to be non-transactional. Setting up such an API key is a critical part of common configuration. if someone has an active session in the admin UI, they can also modify the configuration to make the webhook non-transactional.
Topics created by dan
-
UNSOLVED locked out of admin UI
Q&A • • dan -
SOLVED Setting a certificate for FusionAuth
Q&A • • dan -
UNSOLVED Seeing "alternativeLogins" error
Q&A • • dan -
SOLVED Passing data from login form to webhook
Q&A • • dan -
UNSOLVED What can I do for my customer support reps?
Q&A • • dan -
SOLVED Investigating 2FA failures
Q&A • • dan -
SOLVED Forwarding logs to a logging system
Q&A • • dan -
UNSOLVED Change password flow across devices
Q&A • • dan -
SOLVED webhook/cookies
Q&A • • dan -
SOLVED size of auth header
Q&A • • dan -
SOLVED Contract vs month to month?
Q&A • • dan